Video Progress Bar is a single-page tool for the common video editing and conversion task it is named after. Add a clean, animated progress bar to the top or bottom of any video. The bar grows from left to right as the video plays. Pick the thickness, color, and an optional translucent track. Files are processed entirely in your browser with FFmpeg WebAssembly. The interface keeps the input on one side, the configurable options in the middle, and the result on the other side. Most jobs start and finish without any scrolling.
Behind the controls you see, FFmpeg compiled to WebAssembly is doing the actual video editing and conversion. MP4, WebM, MOV, MKV, AVI, FLV, and OGV are first-class formats and the engine produces a deterministic output for any given input + options combination — useful when you need to re-run a job and expect identical results.
Video Progress Bar is a static page plus a client-side engine. The browser does the work; there is no separate backend in the loop for the actual processing. That architecture is why the tool starts immediately, why it does not depend on the load on a remote service, and why running multiple jobs in a row does not slow it down.
Typical users of Video Progress Bar include students submitting video assignments, product teams shipping release demos and teams compressing demo recordings. The thread connecting all of them is the same: a focused video editing and conversion task that fits cleanly into a browser tab and benefits from a tool with sensible defaults and minimal setup.
Most people land on Video Progress Bar via a search at the moment they actually need the tool. That shapes the design: the page is a single screen with the input on one side, the controls in the middle, and the result on the other, so a first-time visitor can complete the job without reading documentation.
On limits: 500 MB per file is the ceiling. Output formats and quality settings are listed in the controls panel above, and they apply to every run.
As a workflow component, Video Progress Bar is the part you reach for when a single, well-defined video editing and conversion step needs to happen. It performs that step and returns a standard file you can carry into the next part of your pipeline.
The transformation in Video Progress Bar is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.
The download is delivered as `{name}-edited.{ext}` the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.
Some context on why Video Progress Bar exists in this form: modern File APIs, high-performance JavaScript engines, and well-maintained open-source libraries now make it possible to perform video editing and conversion work entirely in the browser. Video Progress Bar is built on top of that capability, which is why a single page can host the full pipeline.
Video Progress Bar produces deterministic output: the same input plus the same options always produces the same result. That predictability matters when the result has to match an upstream specification or be reproducible later.
Tips from users who reach for Video Progress Bar regularly: process one input first to confirm the settings produce what you expect before committing to a batch; treat the page as the working surface and avoid leaving large jobs running in a backgrounded tab where the browser may throttle JavaScript; and if a particular file fails, check whether the source is intact by opening it in its native viewer — most "tool errors" are actually input errors.
When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow FFmpeg compiled to WebAssembly to load.
Open the workspace above to start using Video Progress Bar. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
A WebAssembly build of FFmpeg loads in this page and uses the drawbox filter with a width expression driven by FFmpeg's playback time variable. The bar grows from 0 to the full video width over the clip's duration — entirely on your device.
Drawing the bar over every frame requires re-encoding the video. Server tools use native multi-threaded FFmpeg; the WebAssembly build is single-threaded and typically 4–8× slower. The trade-off is total privacy — your footage never leaves your device.
Progress bars are the social-media gold standard — they tell viewers exactly how long is left so they're less likely to scroll away. Used heavily in TikTok, Reels, Shorts, and educational explainers.
Yes. Bottom is the default and matches the YouTube / TikTok convention. Top works well when the bottom of your video already has captions or branding.
4–8 px is sleek and modern. 10–16 px is the chunky "TikTok progress bar" look. 20–40 px is dramatic and works for short hooks where the bar should be the main visual signal.
A faded version of the track color drawn across the entire width of the video, behind the colored progress bar. It gives the bar context — viewers see how much is left as well as how much has played.
Up to 500MB. The encode runs at roughly real time on a modern desktop and is slower on mobile.
No. The rendering runs entirely in your browser tab. Nothing is transmitted, stored, or logged. Closing the tab erases the file from memory immediately.
Video Progress Bar is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (FFmpeg compiled to WebAssembly) is open-source and can be used directly from your own code.
Video Progress Bar runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 500 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Video Progress Bar works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is one of MP4, WebM, MOV, MKV, AVI, FLV, and OGV and that it is below 500 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Video Progress Bar is built on FFmpeg compiled to WebAssembly, which is the same class of engine used by professional video editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Your file is processed inside your browser by FFmpeg compiled to WebAssembly. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
Video Progress Bar is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript and WebAssembly to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (FFmpeg compiled to WebAssembly) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Video to GIF
Convert any video clip to an animated GIF entirely in your browser. Pick the start, length, frame rate, and width — your file is processed locally with FFmpeg WebAssembly and never uploaded.
Screen Recorder
Record your screen, a window, or a browser tab directly in your browser. Optionally include system audio and your microphone. Capture, preview, and download the video without installing any app — and without uploading anything.
Webcam Recorder
Record your webcam directly in your browser with optional microphone audio. Pick the resolution (480p, 720p, or 1080p), frame rate, and mirror mode, then capture and download the result without installing any app.
Screen + Webcam Recorder
Record your screen with your webcam composited into a picture-in-picture corner — perfect for tutorials, course videos, demos, and reaction recordings. Pick the camera position, size, and audio sources, then capture and download in your browser.
Video Slideshow Maker
Turn a stack of photos into an MP4 slideshow with per-slide durations, crossfades, and an optional soundtrack. Pick the resolution (up to 1080p), frame rate, and transitions, then download a single MP4 — all processed in your browser with FFmpeg WebAssembly.
Video from Images + Audio
Combine a stack of photos with a music track or narration into a single MP4 video. Pick the resolution, per-slide duration, transitions, and let the slideshow length match the audio. All processed in your browser with FFmpeg WebAssembly.
Video Trimmer
Set precise in and out timestamps, snap to keyframes when needed, and document handles for social-safe cutdowns.
Video Splitter
Split any video into 2–10 equal-length pieces, packaged as a downloadable ZIP. Files are processed entirely in your browser with FFmpeg WebAssembly using lossless stream-copy.