Render & Export
A compiled render sidecar that benchmarks your machine's truth
Rendering doesn't run in the app window. It runs in a compiled binary shipped alongside it, with the Rust compositor, ffmpeg, and ffprobe staged as real resources — so an export can't be slowed down, throttled, or killed by the UI.
- Engine
- Remotion in a compiled sidecar
- Transport
- NDJSON progress stream
- Binaries
- Rust compositor · ffmpeg · ffprobe
- Encoder choice
- auto · gpu · cpu
- Concurrency
- Auto, memory-aware
[How it works]
Render & Export in three moves
Choose the output
Codec, resolution by short edge, bitrate, and quality — with the container picked for you from the codec.
Tune if you want to
CRF from 14 to 34, all ten x264 presets, JPEG or PNG intermediate frames, and explicit GPU or CPU encoding.
Watch it work
Progress streams back as NDJSON and the overlay shows a live composition frame — you see the actual output, not a spinner.
[Under the hood]
Built to be used, not just demoed
The details that separate a party trick from a tool you reach for daily.
Probed hardware encoders
ReelM asks ffmpeg which encoders exist on your machine instead of assuming from the platform — so a Windows build without NVENC doesn't promise it.
CRF is never silently dropped
Automatic encoder selection respects an explicit CRF. If honouring your quality target means using the CPU encoder, it uses the CPU encoder.
Memory-aware concurrency
Automatic concurrency weighs core count against a real memory ceiling, because free-memory reporting lies on macOS and Linux.
GPU rasterisation, measured
GPU rasterisation ships off by default — because in benchmarks the headless renderer beat the GL-backed path by roughly 3×.
Preview quality tiers
Playback can drop to a proxy tier while you scrub; the export always uses the highest available quality.
Frame-exact stills
Single frames and contact sheets render through the same composition selection as the export, so a still is a true preview of the output.
[The full inventory]
Everything in Render & Export
NO MARKETING ROUNDING. THESE ARE THE ACTUAL NAMES IN THE APP.
Codecs & containers
- H.264
- mp4
- H.265 / HEVC
- mp4
- VP8
- webm
- VP9
- webm
Output settings
- Resolution
- 480p · 720p · 1080p (short edge)
- Bitrate
- 2 · 5 · 10 Mbps, or 1–60 custom
- CRF
- 14–34 (default 18)
- Frame format
- JPEG (fast) · PNG (lossless)
- Aspect
- Project aspect preserved
x264 presets
Hardware encoders considered
Probed per machine; unavailable ones are never offered.
[ReelMy · agent surface]
Ask for it instead of clicking it
ReelMy can't start an export, but it can look — stills and contact sheets let it check its own work before handing the project back.
All 79 tools[Questions]
Render & Export, answered
Export presets currently top out at 1080p on the short edge. Higher output tiers are on the roadmap; the pipeline itself is resolution-agnostic.
No. Rendering is entirely local — the compositor, ffmpeg, and the composition bundle all ship with the app.
Because we benchmarked it. The headless renderer was about three times faster than the GL-backed browser on the same project. You can still force it on.
[Launching July 22, 2026]
Your next reel is one prompt away
Get early access before July 22, 2026 — no card, no watermark. The moment it lands, ReelMy cuts the first pass while you grab coffee, then you take the timeline as far as you want.