When you know the exact flags
FFmpeg online
Reuse a command from a script, README, or Stack Overflow answer with minimal changes.
Convert video presets
Better when you want MP4/WebM/GIF output without memorizing codec names.
FFmpeg Online — Run Custom Commands in Your Browser
Run custom FFmpeg commands in the browser with INPUT and OUTPUT placeholders. For people who already know FFmpeg flags and want local processing without installing tools.
Choose a video to start
Drop a file here, upload from your device, or open your library.
Who this page is for
If you already run ffmpeg in Terminal and just need a browser-based file picker, this is the right page. You compose the argument list, vdoflow maps INPUT to your source file and OUTPUT to the export path, and processing stays on your device.
If you do not know FFmpeg yet, start with convert, trim, or resize presets instead. They encode safer defaults and skip the trial-and-error of raw flags.
Custom FFmpeg vs guided presets
Debugging failed exports
FFmpeg online
You read stderr, adjust flags, and retry — same muscle memory as desktop FFmpeg.
Guided tools
Fewer knobs, fewer ways to break playback compatibility.
Browser limitations
FFmpeg online
WebAssembly build — not every desktop encoder or hardware path exists here.
Guided tools
Stay inside supported presets that vdoflow tests for browser export.
Starter commands that map cleanly to INPUT and OUTPUT
Trim without re-encoding when stream copy works: -ss 00:00:05 -to 00:00:15 -c copy. Adjust the timecodes for your clip.
Scale to 1280px wide while keeping aspect ratio: -vf scale=1280:-2. Add a video codec if copy mode is not enough.
Mute audio: -an. Useful before adding a new soundtrack elsewhere.
Always test on a short clip first. Long GOP sources and heavy filter graphs can be slow in the browser even when they feel instant locally.
Not every desktop command works here
Browser FFmpeg is a constrained runtime. Hardware encoders, some filters, and exotic codecs from your local install may be missing. Read FFmpeg in the browser before you assume a Terminal command will behave the same way online.
How to run a custom FFmpeg export safely
- 1. Load a short test clip: Use ten to twenty seconds of representative footage before you point a long command at a full source.
- 2. Write arguments with INPUT and OUTPUT tokens: Keep INPUT and OUTPUT in the command string. vdoflow substitutes your picked file and export path.
- 3. Read errors, simplify, and retry: Remove filters one at a time until the export succeeds, then add complexity back gradually.
FAQ
What are INPUT and OUTPUT?
Placeholders in your command string. vdoflow replaces INPUT with your source file path and OUTPUT with the export destination inside the browser runtime.
Why did my command fail?
Common causes: unsupported codec or filter in the WASM build, typo in flags, or a stream-copy attempt on a clip that needs re-encoding. Simplify the command and retry on a short clip.
Can I use hardware acceleration?
No. Browser FFmpeg runs in WebAssembly without GPU encoders. Expect CPU-bound exports comparable to software encoding on desktop.
Related tools and guides
FFmpeg in the Browser
Read how WASM FFmpeg differs from a local install before debugging failed commands.
Convert Video
Use guided presets when raw arguments are more complexity than you need.
Trim Video
Shorten the source before long encodes or heavy filter graphs.
Resize Video
Normalize resolution when delivery targets expect 720p or 1080p output.
When presets are enough
Start with one focused workflow and keep the suggested settings ready when the page opens.
Embed this tool
Use the same vdoflow tool inside your own docs, product pages, or support articles.
<iframe
title="vdoflow embedded video tool"
src="https://vdoflow.com/embed/ffmpeg-online"
width="100%"
height="760"
style="border:0;"
loading="lazy"
allow="clipboard-write"
></iframe>