What is a Video Compressor?
Video is large because it stores every frame, and it stores every frame at whatever quality the camera or screen recorder chose. A minute of 1080p phone video is roughly 100 to 200 MB; the same minute at 480p and a lower bitrate is under 20 MB, and on a phone screen the difference is far smaller than the numbers suggest.
Compression means re-encoding: decoding each frame and writing it again at a lower resolution, a lower bitrate, or both. Resolution is the bigger lever, because bitrate scales with the number of pixels — halving the width and height quarters the pixel count, and the encoder can then hit a much lower bitrate while keeping the same visual density. The bitrate setting here is derived from the output size and frame rate rather than typed in, which is what keeps the file predictable.
The awkward part is where the encoding happens. This tool uses the browser's own recorder — the same mechanism a screen recording uses — so the video is drawn frame by frame onto a canvas as it plays and captured in real time. Nothing is uploaded and no server does the work. The cost is time: a two-minute clip takes two minutes, and a dedicated two-pass encoder would still produce a smaller file for the same quality.
How to compress a video
- Choose the video. Its duration, resolution and size are read from the file in your browser, and nothing is sent.
- Trim the clip if you only need part of it. Compressing ten seconds instead of ten minutes is faster and smaller.
- Set the resolution. 1280 or 854 px covers almost every sharing use; keep the original size only when detail genuinely matters.
- Pick a quality. Balanced is the sensible default; choose Small for messaging, High when text or fine detail is in the frame.
- Press Compress and leave the tab open. The capture runs in real time, so note the estimate next to the button before starting.
- Play the result back in the page and compare it with the original before you download, then keep the original until you are satisfied.
Video Compressor limits and rules
| Item | Limit |
|---|---|
| Capture | Realtime, via the browser's own recorder — about one second per second of video |
| Output container | MP4 where the browser supports it, otherwise WebM |
| Resolution ceilings | Original, 1920, 1280, 854 or 640 pixels wide, aspect ratio preserved |
| Quality settings | Roughly 0.05, 0.09 and 0.15 bits per pixel per frame |
| Audio | Kept, at 128 kbit/s, routed through the browser's audio graph |
| Frame rate | Captured at 30 fps whatever the source is; a 60 fps source is halved |
| Capture speed | 1×, 1.5× or 2× — faster capture drops frames and makes motion choppier |
| Long videos | Possible but slow, and the tab must stay in the foreground on mobile |
| Stopping early | The Stop button keeps what has already been recorded as a shorter clip |
| Uploading | None — the file is decoded from local memory and never leaves the machine |
When to use it
- Getting a clip under a messaging app's size limit without sending it to a conversion site.
- Shrinking screen recordings before attaching them to a bug report or a ticket.
- Cutting a two-second highlight out of a long recording to paste into a chat.
- Making a small version of a video for embedding in a slide deck or an email.
Is it private?
The video stays on your machine for the whole process. It is decoded by your browser, drawn to a canvas in this page and re-encoded by the browser's own recorder, so no part of the file is uploaded, queued or stored anywhere. This is also why the tool keeps working with the network disconnected, and why closing the tab ends everything.
Frequently asked questions
Because the browser records in real time — it is capturing a stream as it plays, not running a batch encoder. A 90-second clip takes about 90 seconds, or 45 at the 1.5× capture setting. This is the price of doing the work locally with no upload and no server. The trade is deliberate: an upload-and-wait service would be quicker per megabyte, but your file would sit on somebody else's disk.
Yes, unavoidably — re-encoding always does, because every frame is decoded and compressed again. At 720p with the balanced setting the loss is hard to see on a phone or a laptop screen. The places it shows are fine text, fast motion and gradients. Always compare the result with the original in the page before deleting anything.
Because the browser chose the container. Safari records MP4 with H.264, and recent Chrome builds can too; Firefox and older Chrome builds record WebM with VP8 or VP9. Where MP4 is available it is preferred, since it plays in more places, including older editors and QuickTime. The result panel names the format you actually got.
There is no server limit, so no 100 MB or 500 MB ceiling — the only constraint is your machine's memory and how long you are willing to wait. A 2 GB file will decode slowly and a very long one risks exhausting memory in the tab on a phone. Desktop browsers handle an hour of footage; a phone browser is happiest under ten minutes.
Yes. The audio is routed through the browser's audio graph and added to the recorded stream at 128 kbit/s, so it comes out as a normal stereo track. During capture the clip plays silently, which is intentional — the recorder is capturing the audio while the speakers stay off.
It happens when the source was already encoded efficiently, or when it is very short: container and track overhead is a real cost on a five-second clip. The result panel says so rather than pretending otherwise. Choose a smaller resolution, drop the quality setting, or use the original file as it is.
Related tools
Written and maintained by Md. Nur Hossain Repon.