Upload-first workflow
Drag in multiple clips and one soundtrack with clear validation, remove controls, and responsive feedback.
FFmpeg-backed auto editing for creator teams
Turn raw clips into a client-ready edit in minutes.
EditForge ingests multiple source clips plus one soundtrack, builds a paced timeline automatically, normalizes the footage, and exports a finished MP4 you can review immediately.
Secure uploadsAudio-driven timingDownloadable render
Output formats
3
Auto pacing styles
4
FFmpeg export
MP4
Render board
Promo edit A-12
Live
Source clips12 loaded
Audio-driven assembly
Trim, normalize, concat, soundtrack overlay
Average turnaround
< 2 min
How It Works
A startup-grade workflow with a practical render engine underneath.
EditForge focuses on the first version that actually works locally: secure uploads, clear options, FFmpeg orchestration, and a polished review experience.
Audio-timed pacing
The MVP timeline builder repeats and trims clips to cover the soundtrack duration without manual editing.
Format presets
Export for vertical, horizontal, or square delivery with normalized resolution, crop, and frame rate.
Reliable FFmpeg pipeline
Every render goes through a predictable normalize, segment, concat, and audio-overlay sequence for local stability.
Job polling
The editor reports queue, processing, completion, and failure states so users are never left guessing.
Cleanup aware
Uploads and intermediate files are removed after successful renders, and stale jobs are purged on a rolling TTL.
Pipeline
From uploads to export without manual editing.
1
Upload your source clips and one soundtrack.
2
Choose format, pacing profile, and ordering rules.
3
Generate the edit, poll progress, review the MP4, and download it.
Secure handling
Files are renamed and written into isolated per-job directories.
Export consistency
Every source clip is normalized to the selected resolution and 30 fps.
Simple scaling
The first version stays on the safe path: no fragile AI transitions or unreliable browser encoding.
Product polish
Landing, editor, progress, and download flows feel like one coherent product.
Pricing Mockup
Positioned like a real product, even in MVP form.
The current app runs locally, but the pricing model frames where the product can go once the editing pipeline is productionized.
Starter
$0/ month
Prototype your edit flow locally.
- Single local workstation
- FFmpeg render pipeline
- One active export at a time
Studio
Most likely$29/ month
The product positioning most teams would expect.
- Priority render queue
- Brand presets and style packs
- Cloud storage handoff
Scale
$149/ month
For agencies producing repeatable campaign edits.
- Multi-user workspaces
- Webhook callbacks
- Managed render infrastructure
FAQ
Clear constraints, no fake magic.
The app is intentionally honest about the first release: it renders real edits, keeps the pipeline understandable, and leaves room for smarter sequencing later.
What does the first version of EditForge actually automate?
It trims and reuses uploaded clips to cover the soundtrack duration, normalizes every segment to a consistent frame size and frame rate, concatenates the result, and overlays the audio into a final MP4.
Does it do beat detection or AI shot selection?
Not in this MVP. The editing styles currently change pacing rules and timeline behavior rather than using model-based media analysis. That keeps the local build reliable.
What does the server need to run?
A Node 20 environment plus FFmpeg and FFprobe installed locally or exposed through the `FFMPEG_PATH` and `FFPROBE_PATH` environment variables.
Can I use this for real deliverables?
Yes for simple draft generation. It is designed as a working foundation: stable local rendering, polished UX, and a clear extension path for smarter shot selection later.