Want to do it rather than read about it? The tool is on the main page — pick a preset, drop a clip, done.
If you landed here because you need a video under 20 MB to send on Discord, you want a video compressor, not this. A compressor keeps the resolution and the frame rate and lowers the bitrate — the picture stays as close to the original as possible. Use one of those; it will do a better job for that problem.
If you landed here because you want the picture itself to look older, cheaper, or lower-fidelity — like it was shot on a 2005 phone, a camcorder, or a security camera — then lowering the video quality is the goal, not a side effect. That is a different job, and it needs different controls.
Most pages that rank for "lower video quality" or "reduce video quality" are compressors answering the first question. This one answers the second.
What "lower video quality" actually means here
Three things change the character of a moving image:
- Resolution — how many pixels are really there. 256×144 stretched back to full screen gives you visible, chunky pixels. That is the single strongest signal of "old device."
- Frame rate — how many moments per second were captured. 12 or 15 fps reads as cheap hardware; 30 fps reads as modern, no matter how blurry it is.
- Color and encoding character — washed-out contrast, color bleed, banding, the slight blockiness of an old codec. This is seasoning, not the meal.
In a compressor, all three are costs to be minimized: you lower the bitrate and hope nobody notices. Here they are controls you turn up on purpose. A 144p, 15 fps clip with slightly crushed color is not a failed encode — it is the deliverable.
That inversion is the whole difference. Same encoder, opposite objective.
Why compressing harder doesn't get you there
A tempting shortcut: just crank the quality slider down. It doesn't work, and the numbers show why.
HandBrake — a desktop transcoder built on the same x264 encoder used by browser-based tools — recommends RF 20–24 for 1080p and describes anything above RF 30 as having "significant compression artifacts… acceptable for previews or throwaway encodes only." In a published x264 test on a 9-second 720p clip, pushing all the way to RF 34 shrank the file from 10.1 MB to 0.7 MB, but SSIM against the source was still 0.881.
That number is the point. At the most aggressive setting a mainstream tool considers usable, the picture is still statistically close to the original. What you get is a clean video with blocky artifacts — not a video that looks like it came from another era.
You cannot arrive at "looks like a 2005 camera phone" by optimizing for "looks like the original." The two objectives point in opposite directions. Compression artifacts are damage; the low-fi look is a style. Adding damage to a modern image does not age it.
Rule of thumb: if someone looks at your result and says "the quality dropped," you compressed. If they say "what year is that from?", you lowered the quality on purpose.
What actually produces the "old device" look
The period feel comes from spatial and temporal sampling, not bitrate.
| Axis | What to change | What it reads as |
|---|---|---|
| Resolution | Downscale to 144p / 240p / 360p, then let the player scale back up | Cheap sensor, visible pixels |
| Frame rate | Drop to 12 / 15 fps | Old hardware, slightly stuttery motion |
| Color | Mild desaturation, lifted blacks, slight color bleed | Aged tape / early digital camera |
| Codec character | Light blockiness, softer edges | Early-2000s compression |
Resolution does most of the work. Downscaling throws away real detail and then reconstructs a coarse image — that is exactly what a low-end sensor would have captured. Frame rate is second: motion is where "cheap" becomes obvious. Color and codec character only sell the effect once the first two are right; applied to a sharp 30 fps clip, they just look like a filter.
This also explains why a "quality" slider on a compressor is the wrong instrument. It changes one number (bitrate) while holding the two that matter (resolution, frame rate) constant.
When people actually want this
Lowering quality on purpose shows up in a handful of recurring situations:
- Memes and reaction clips — a slightly degraded repost reads as authentic in a way a pristine 4K render doesn't.
- AI-generated video — synthetic footage is often too clean. A low-resolution, low-frame-rate pass makes it believable as found footage.
- Period pieces and retro edits — Y2K camcorder, VHS, early smartphone, CCTV.
- Simulated found footage — security cameras, dashcams, phone recordings used as props.
- Game and screen captures — matching in-game or archived footage to an older aesthetic.
- Social posts — deliberately "bad" quality is a visual register of its own, like a film grain filter but stronger.
None of these has a target file size. The success criterion is whether the look reads correctly, not whether the output is small.
How to lower video quality in practice
The pipeline is short:
- Downscale first — pick the resolution that matches the era you're imitating (144p for a 2005 phone, 360p for an early smartphone, 480p for camcorder or tape).
- Drop the frame rate — 12 or 15 fps for cheap hardware, 24 fps for tape-ish material.
- Then encode — enough bitrate to avoid mush, plus mild color adjustment if the look needs it.
- Check a frame before and after. Because the goal is visual, you need to see it, not just read a size number.
This can run entirely in the browser: the file stays on your device, nothing is uploaded, and you can compare frames before exporting. That matters more than it sounds — a tool that sends your video to a server adds a wait and a privacy question to what should be a quick visual decision.
Lower video quality vs. compress video
| Lower / reduce video quality (on purpose) | Compress a video | |
|---|---|---|
| Goal | Change how the picture looks | Make the file smaller |
| Quality is… | the deliverable | the cost |
| Main control | Resolution + frame rate | Bitrate |
| Success looks like | "That feels like 2005" | "Same video, fewer MB" |
| Typical output | 144p–360p, 12–15 fps | Original resolution, lower bitrate |
| When the picture changes a lot | Success | Failure |
If your brief contains a number in MB, you want the right-hand column. If it contains a year, a device, or a feeling, you want the left one.
FAQ
Is this the same as compressing a video? No. A compressor tries to keep the picture while shrinking the file. Lowering quality on purpose changes the picture itself. If what you need is "under 20 MB for Discord," use a dedicated compressor — it will keep your resolution and only reduce the bitrate, which is exactly right for that job. The presets here deliberately reduce resolution, so the visual change is much larger than you'd want from a compression pass.
Will the file also get smaller? Yes, as a side effect — a 144p, 15 fps clip is small. But that is a consequence, not the target, and we don't optimize for it.
What resolution should I start with? 360p is a safe first look. Go to 240p when it should feel like an old phone, 144p when the pixels themselves should be visible. Pair it with 15 fps before you touch color.
Does this replace my original file? No. You export a new file; the source is untouched.
Do I have to upload my video? No. Processing can happen locally in the browser, so there is no upload step and nothing is stored on our side.