rea-video is a free, open source ai development platforms project written in Python and released under Apache-2.0. It has 6,262 GitHub stars, 895 forks and 4 open issues, and was last pushed 4 hours ago. On this registry it ranks #94 of 163 tracked projects in AI Development Platforms, with 5 head-to-head comparisons available.

What is rea-video?

rea-video is an Apache-2.0 Python command-line tool that runs inside AI coding agents such as Claude Code or Codex to reverse-engineer any video shot by shot — deciding whether each shot was filmed, AI-generated or coded — and to return a plan for remaking it, for creators, marketers and developers who need to reproduce a reference video rather than guess at how it was made.

What it is

rea-video is a Python package (Python 3.10 or newer) that installs as an agent skill rather than as a standalone application. scripts/install_skill.sh installs the CLI with pip, pipx or a local .venv and links the skill into ~/.claude, ~/.codex and ~/.agents, so an agent that can run commands learns the workflow and drives the analysis itself. The tool relies on ffmpeg for media handling, and it can optionally be pointed at a video-capable model endpoint — Gemini and Doubao are both named as working options — by giving the agent the endpoint and key, which sharpens the live/AI/3D calls and adds a reverse-engineered prompt for every shot.

The problem it solves is the manual teardown of a reference video. Instead of scrubbing a timeline frame by frame to work out which parts were shot on a phone, which came from a text-to-video model and which were built in code, the tool judges each shot separately across the categories it documents — live footage, AI video, avatar, 3D or animation, code or template, screen recording, and mixed edits — and then reassembles those verdicts on the original timeline. For code-built sequences such as kinetic type, UI demos, charts and slide-style cards, the breakdown of text, layout and motion timing is delivered ready to rebuild as a Remotion project, and styled captions export to SRT or ASS.

Key capabilities

  • Classifies every shot as live footage, AI video, avatar, 3D/animation, code/template or screen recording, then reassembles the shots on the original timeline.
  • Produces a one-line summary of the whole video, such as "41% AI video + 59% code UI, 8 s of real screen recording, library music at 122 BPM".
  • Splits the output into a remake plan covering what to film, what to generate and what to code.
  • Generates a full report.html with per-shot frames, evidence, prompts, camera and lighting notes, and an audio breakdown.
  • Documents live-footage craft in detail: setups and camera positions, framing, camera moves, lighting with gear lists across 12 setups, and color grade.
  • Reverse-engineers a prompt per shot for AI video, including how to batch shots into generations and which model to use, when a video-capable model is connected.
  • Covers captions and overlays — line start and end times exported to SRT or ASS, color and outline, text entry animation, and the position and duration of stickers, emoji and picture-in-picture — plus cut placement and editing pace.

Who uses it and how

  • Marketing and creative teams taking apart a competitor's TikTok ad, as in the README example where one video resolves to live footage on a single set with two camera positions and the other to 8 AI shots across 3 generations.
  • AI video producers working on text-to-video, image-to-video, AI short drama and AI music video, who need a per-shot prompt and a batching strategy rather than a single vague description.
  • Motion designers and front-end developers rebuilding kinetic type, UI demos, charts and slide-style cards as Remotion projects.
  • Software teams analysing tutorials and web demos, where the breakdown identifies which parts are real screen material that has to be recorded by hand.
  • Agent-first workflows: the tool is invoked conversationally from Claude Code, Codex or any command-capable agent, and reports are written in whichever language is requested, Chinese or English.

Getting started

The documented path is to tell an agent "Install https://github.com/JuneYaooo/rea-video, then break down this video: /path/to/video.mp4", and the agent installs the CLI, learns the workflow and runs the analysis. Manual installation requires ffmpeg and Python 3.10 or newer: clone the repository, run bash scripts/install_skill.sh, then confirm with rea-video --help.

How it compares

The facts provided name no directly comparable reverse-engineering tool, so rea-video stands alone in this registry. The neighbouring projects it touches are dependencies rather than rivals: ffmpeg is a prerequisite it drives, and Remotion is a target format its code-and-template breakdowns are built to feed.

When to use it — and when not to

Choose it when the work already happens inside an agent and the goal is a reproducible remake plan rather than a description: ffmpeg and Python 3.10 or newer are the only hard requirements, and the video-model endpoint is optional. Expect to supply that endpoint and key if per-shot prompts and confident live/AI/3D calls matter, because without one the tool falls back to the agent inspecting uncertain shots itself. Anyone wanting a graphical application, or a workflow that does not involve a command-capable agent, should look elsewhere, since the documented interface is the CLI plus the installed skill.

project readme (upstream, from github) — read inline

Reverse-engineer any video.

Shot by shot: was it filmed, AI-generated or coded, and how to remake it.

Website | 中文 | English | Русский | 日本語 | 한국어 | Español | Português | Français | Deutsch

Stars Python Agent

JuneYaooo/rea-video | Trendshift

Visit our website Join our Discord Follow on X

⭐ Help more people find rea-video. Star this repo!

Left: a TikTok ad shot on a phone. Right: an AI remake with another product. rea-video's verdict: the left is all live footage, one set and two camera positions; the right is all AI, 8 shots across 3 generations.

Quick start

rea-video is built for AI agents. In Claude Code, Codex or any agent that can run commands, say:

Install https://github.com/JuneYaooo/rea-video, then break down this video: /path/to/video.mp4

The agent installs the CLI, learns the workflow and runs the whole thing. You need ffmpeg and Python 3.10+.

Install by hand
brew install ffmpeg            # or: sudo apt install ffmpeg
git clone https://github.com/JuneYaooo/rea-video && cd rea-video
bash scripts/install_skill.sh  # installs the CLI (pip, or pipx / a local .venv if pip is blocked) and links the skill into ~/.claude, ~/.codex, ~/.agents
rea-video --help

You get:

  • a one-line summary, e.g. "41% AI video + 59% code UI, 8 s of real screen recording, library music at 122 BPM"
  • a remake plan, split into what to film, what to generate and what to code
  • a full report.html with per-shot frames, evidence, prompts, camera and lighting notes, and the audio breakdown

You can also hook up a video-capable model (Gemini or Doubao both work) by giving the agent its endpoint and key. That makes the live/AI/3D calls more accurate and adds a reverse-engineered prompt for every shot. It works fine without one; if your agent can see images, it checks the uncertain shots itself.

Reports are written in whichever language you ask in (Chinese or English). The example reports below are in English.

What it can break down

Video type Examples What you get
Live footage Talking-head, tabletop, handheld product demo, vlog, store visit Setups and camera positions, framing, camera moves, lighting (12 setups with gear lists), color grade
AI video Text/image-to-video, AI short drama, AI music video Evidence, a reverse-engineered prompt per shot, how to batch into generations and which model to use
Avatar A portrait driven by audio, lip-sync Which shots are avatar shots, what portrait and audio you need
3D / animation Blender / C4D explainers, product animation, 2D animation, stop-motion Whether to generate with a video model or render from 3D code
Code / template Kinetic type, UI demos, charts, slide-style cards Text, layout and motion timing, ready to rebuild as a Remotion project
Screen recording Software tutorials, web demos Which parts are real material you'll need to record yourself
Mixed / edits AI characters + code UI + real screen capture; live footage with AI edits Each shot judged separately, then reassembled on the original timeline

Besides how the visuals were made, every breakdown also covers:

  • Captions and styled text: start and end of each line (exports to SRT / ASS), plus color, outline and how the text comes in
  • Stickers, emoji, picture-in-picture: where they sit and how long they stay
  • Editing: where the cuts are, how fast, whether they hit the beat
  • Audio: human or AI voice, AI or library music and its BPM, where each sound effect lands
  • Material you'll need to supply yourself: screen recordings, screenshots, product photos

Examples

The sample videos in docs/cases/videos/ are re-compressed to keep the repo small, which strips the TikTok / Douyin platform tags. So if you run them yourself, you'll get different results from the reports below, especially without a vision model. To reproduce them, use the original downloads from the platform.


Mixed-media clip · 19 s · 10 shots
AI characters talking + code-built UI + 8 s of real screen recording. The 5 dialogue shots are broken up by UI segments but share one set, so a single generation covers all of them.
Video · Report

3D explainer · 67 s · 21 shots
All 3D, AI narration. You can do it in 10 video generations, or have an LLM write Blender / Three.js code.
Video · Report

Product promo · 70 s · 12 shots
83% code-driven motion graphics, 12% screen recording. No video model needed; one Remotion project does it.
Video · Report

AI music video · 165 s · 86 shots
Correctly flags the song as AI-generated (it was made with Suno). The vision model called some shots "live-action drama"; the agent spotted fake Chinese characters on a scroll and ruled them AI.
Video · Report

Live-action unboxing · 72 s · 29 shots
All real footage: an overhead phone rig, one rug, one camera position, no voice-over, room sound plus library BGM. After platform transcoding, the offline tools called 35% of it AI; after agent review it came out 97% live-action.
Video · Report

AI + real person hybrid · 58 s · 21 shots
75% real (talking head + filming a phone screen) and 25% AI: the creator fed her own on-camera clip and two product photos to Jimeng to generate a "real-person" product segment. The AI part gave itself away with the Jimeng watermark and garbled text on the gift box.
Video · Report

Remakes

After rea-video breaks a video down, the remake recipe in capsule-cinema generates a new version that keeps the original's camera, motion, pacing and transitions and swaps only the elements you pick. These were made with a self-hosted MiniMax H3, using the original shot as the motion reference and keyframes with the swapped elements (gpt-image-2) for the look. Below are three remakes OiiOii showed in its WeChat articles. We made two versions of each: one with the same swap as OiiOii, and one that also swaps the subject, setting and props. Each GIF plays four versions in sync: the original, OiiOii's remake, our remake and the element-swap version.

Overhead outfit change · 12 s
Same swap: woman → man, three outfits → matching menswear. Element swap: a girl in three historical Hanfu outfits in a Chinese study; the remote becomes a round fan.

HD comparison video (with audio) · same-moment stills
Paper-craft / watercolor animation · 30 s
Same swap: new clay girl as the lead. Element swap: a fox; forest → coral reef, clouds → starry sky, sunset → aurora.

HD comparison video (with audio) · same-moment stills
Handheld product video · 21 s · 11 shots
Same swap: an original new product, English sticker → Chinese caption. Element swap: pink product, kitchen → camping table, new ingredients.

HD comparison video (with audio) · same-moment stills

The HD comparison videos use the original audio. The originals and OiiOii versions come from the articles and are shown for comparison only.

Accuracy

Accuracy of the how-it-was-made call, weighted by shot duration:

Tuning set (15) Holdout (16) Re-encoded WeChat videos (10)
Tools only (offline, free) 98.3% 99.6% / 98.9% 88.6%
+ vision model (Gemini) — 99.6% / 99.8% 99.6%
+ agent visual review — 99.6% / 99.8% 100%

The Holdout column shows two numbers: holdout (9 videos) and holdout2 (7 videos).

On original files, the tools alone are usually enough. Videos downloaded from platforms have been recompressed, which wipes out the noise evidence, so you need a visual check to get back above 99%.

Real-asset detection is 97–99%, and shot boundaries are all correct. Numbers and how to reproduce them: eval/RESULTS.md.

How it works

rea-video pipeline

  1. Split: cut the video into shots and split the audio into voice, music and effects.
  2. Gather evidence: measure (frame cadence, sensor noise, whether the whole image moves as one flat plane, AIGC tags in the metadata), look (hands, text, physics) and listen (BPM, key, singing vs speech).
  3. Decide: hard evidence like AIGC tags and frame cadence beats "looks like". Conflicts get flagged for the agent to check visually.
  4. Plan the remake: batch shots according to what the target video model can actually do, such as max clip length, multi-shot support and how many reference images it takes.

Star History

Star History Chart

FAQ

How is this different from one-click remake tools like Hypit?

Hypit takes a reference video and makes a new one: the agent reads frame grids to understand the original, generates footage with the models it supports (Seedance, PixVerse, MiniMax, Wan and others), and renders captions and motion graphics in HTML.

It doesn't ask how the original was made. A live-action source goes through the same pipeline; it won't tell you how many cameras were used or how it was lit. What AI video it can match depends on the models it supports: no Kling or Veo, no dedicated avatar or 3D path, and no AI music (you bring your own). It's strongest on talking-head, podcast and interview videos that follow a script, and weaker on music-driven edits, product motion graphics and cinematic shorts.

rea-video doesn't render a video. It works out shot by shot whether something was filmed, AI-generated or built in code, then gives a shooting plan, prompts or a code approach for each. For a quick lookalike, Hypit is faster. To understand how the original was made and remake it cheaply, use rea-video. They work fine together.

Do I need a video-capable model? What does it cost?

No. Tools-only mode is offline and free, and already accurate on original files. For recompressed platform downloads, add a video-capable model (Gemini or Doubao both work) or use an agent that can see images; you pay whatever that service charges. Automatic video generation (capsule-cinema) does a free dry run first and only calls paid models after you confirm.

Can it remake the whole video automatically?

Partly. With capsule-cinema installed, AI shots are generated and placed back on the original timeline automatically. You film the live shots from the shooting plan, and the agent writes the code shots as a Remotion project. See docs/replicate.md.

Can I just repost someone else's video?

No. rea-video is for learning a video's structure, pacing and techniques, then remaking it with material you have the rights to. Don't reuse other people's footage, music, characters or likeness. Follow platform rules and local AI-content labeling requirements when you publish.

Docs

The docs are in Chinese for now.

Community

Questions, breakdowns and remake ideas: GitHub Discussions. Chat with us on Discord. Chinese speakers can also find us on linux.do.

Want a video broken down? Open a request issue with the link and we'll publish the result as a case.

Credits

Inspired by REA (Reverse Engineer Anything): work back from what you see to how it was made, back every claim with evidence, and verify by measuring.

Frequently asked questions

Is rea-video free to use?

rea-video is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does rea-video do?

Reverse-engineer any video, shot by shot: filmed, AI-generated or coded, and how to remake it. 逆向一切视频,逐个镜头看是拍的、AI 生成的还是代码做的,再告诉你怎么复刻。

What is rea-video written in?

rea-video is primarily written in Python. Its source is publicly available at https://github.com/JuneYaooo/rea-video, and it has 6,262 GitHub stars.