How browser-based video compression works
A beginner-friendly guide to quality presets, resolution, target size, and why real compression takes time.
September 3, 2026Video files are much larger than most images because they contain a sequence of frames plus audio. FlyThe BG's video compressor is designed around local browser processing where supported, so the source video does not need to be uploaded to a FlyThe BG processing server.
Quality and resolution are different
Resolution controls how many pixels each frame contains. Quality controls how aggressively the encoder compresses those pixels. Dropping from 1080p to 720p can save substantial space, while lowering quality can reduce size without changing the frame dimensions.
Target size is an estimate
A target-size workflow can calculate an initial bitrate from the requested size and video duration, then encode and measure the actual output. Because containers, audio, motion, and encoder behavior affect the final file, the requested number is a target rather than a promise.
Why progress is real
Encoding has to read, decode, process, encode, and mux video data. A real local compressor can therefore take noticeable time on a phone or laptop. Progress should reflect actual processing rather than an artificial timer.
Ready to try it?
Use the FlyThe BG tools directly in your browser and choose the workflow that fits your task.
Explore FlyThe BG tools ↗