Sharper, brighter, bigger
Phone footage is dark, compression eats the edges, and a clip shot at 720p has to fill a 1080p timeline. The enhancer measures a few frames first — light, contrast, texture — and then applies the passes that footage actually needs, in an order that does not make it worse.
The AI Video Enhancer improves a soft or noisy video with one preset: it upscales, denoises, sharpens and corrects brightness, contrast and saturation. Upscaling adds pixels, not detail, so a 480p source enlarged to 1080p still holds 480p of information.
How it works
Add the video
Open the footage that needs to look sharper.
Choose the enhancement
Set the upscale factor and how much noise to remove.
Download the result
Save the enhanced video.
The passes, in order
Order is the whole trick. Denoise before sharpening, because sharpening noise turns it into detail-shaped garbage. Scale before sharpening, because scaling softens the edges you just created. Encode last, once.
- 1movieDecodeevery frame, in memory
1920 × 1080 - 2blur_onDenoisegrain and sensor noise
hqdn3d 3 - 3wb_sunnyLightshadows lifted, contrast set
eq + curves - 4aspect_ratioScalelanczos, no softening
3840 × 2160 - 5auto_fix_highSharpenedges only, after scaling
unsharp 0.8 - 6saveEncodewritten on your device
H.264 CRF 20
Presets that match the problem
| Preset | What it changes | Footage it suits |
|---|---|---|
| Sharpen & clarity | unsharp on luma only, mild contrast | Well-lit footage that looks soft after compression |
| Low light rescue | Brightness up, contrast up, light denoise first | Indoor phone clips, evening shots, dark rooms |
| Rescue a soft video | Stronger sharpening, 1.5× scale | Old recordings, out-of-focus footage, VHS transfers |
| Denoise a noisy video | hqdn3d before anything else, no sharpening | High-ISO footage, grain, compression blocking |
| 2× upscale for HD | Lanczos scale, light denoise, sharpen after | 720p material for a 1080p or 1440p timeline |
Four frames are sampled across the clip and reduced to 160 × 90 pixels. From those the tool reads the average luminance (how dark the picture is), the standard deviation of luminance (contrast), and the average difference between neighbouring rows, which is a decent proxy for grain and compression noise. The recommendation follows those three numbers, not a model.
Scaling resamples existing pixels with a Lanczos kernel: edges stay clean, but detail that was never recorded cannot appear. Upscaling helps material that was downscaled before delivery, and it helps when the destination requires a larger frame. It does not turn a blurry shot into a sharp one — for that, sharpening does the visible work, and it has limits too.
Fastest encodes about three to five times quicker with a slightly larger file. Balanced is the default for anything under five minutes. Best quality is worth it for footage with gradients, fog or dark skies, where a low bitrate produces visible bands.
- check_circleWatch a dark scene, not the daylight one
- check_circleKeep denoise under 5 unless the grain is heavy
- check_circleSharpen after scaling, never before
- check_circleStay at 1× if the delivery is the same size
- check_circleCompare the result with the original, side by side
Enhancer questions
Is a real AI model used?expand_more
How much can I upscale?expand_more
Why is my export taking so long?expand_more
Will the audio be kept?expand_more
Can I enhance a vertical video?expand_more
Does it remove compression blocks?expand_more
What Actually Improves a Bad Video
Every “enhance” button promises the same thing: the footage you have, looking like the footage you wanted. The honest version is narrower. A few specific defects can be reduced, in a specific order, and everything else is a trade.
Defect one: not enough light
Dark footage has two problems at once. The picture is dim, and the sensor compensated with gain, which brought noise. Lifting the brightness without touching the noise makes the noise brighter too, so the first pass must be a light denoise, then a tone curve, then a small amount of contrast to keep the blacks black.
Overdoing the lift is the classic mistake. Shadows that are pushed three stops turn grey and plastic. One stop, maybe a stop and a half, is the practical range.
Defect two: softness
Sharpness is local contrast at edges. An unsharp mask increases it by subtracting a blurred copy of the image from itself, which is why it also amplifies grain: grain is local contrast. The amount matters more than the radius — 0.6 to 1.0 is usually enough; 2.0 produces halos that look worse than the original softness.
Defect three: resolution
Upscaling is resampling, not magic. A Lanczos kernel reconstructs edges from the pixels that exist, which is genuinely better than a naive stretch, but no algorithm can recover detail that was never captured. Where upscaling does help is delivery: a 720p source in a 1080p timeline, or a platform that refuses anything below a threshold.
Defect four: compression
Low-bitrate video shows blocks in flat areas and mosquito noise around edges. A small amount of temporal denoising softens both; a large amount smears motion. If the source is very compressed, the better answer is often to keep the frame size and raise the output bitrate rather than to sharpen.
The order that works
Denoise, correct the tone, scale, sharpen, encode. Each step assumes the previous one has already happened: sharpening before scaling wastes detail on pixels that are about to be resampled, and denoising after sharpening fights the edges it just created.
Then compare. Put the original and the result side by side at 100% and ask which one you would rather watch. If the answer is the original, the preset was too strong — and that is a perfectly good result.
Finish the job with these
fact_checkQuick facts
- Upscaling multiplies the pixels, not the detail: a 480p source enlarged to 1080p still holds 480p of information.
- Sharpening and denoising work against each other, because every sharpening pass amplifies the noise the denoiser just removed.
- H.264 is the codec that made HD video practical on the web: it is decoded by every current browser and phone without a plugin.menu_bookITU-T
- Lowering the bitrate of H.264 throws away detail in fast movement first, which is why sport and confetti are the hardest scenes to compress.menu_bookITU-T
- WebAssembly became a W3C Recommendation in 2019 and lets a page run a full encoder such as FFmpeg without a plugin.menu_bookW3C
helpQuestions people ask
Can AI make a low-resolution video look sharper?expand_more
What does video denoising do?expand_more
Does enhancing a video make the file bigger?expand_more
hubWhat this page is about
- H.264 / AVCopen_in_new
The video codec standardised by ITU-T as H.264 and by ISO/IEC as MPEG-4 AVC, decodeable by every current browser.
- WebAssemblyopen_in_new
A binary instruction format for the browser, standardised by the W3C, that runs code compiled from C, C++ or Rust at near-native speed.
- Web Audio APIopen_in_new
The W3C API that builds an audio graph in the browser and can render it faster than real time with an OfflineAudioContext.
library_booksOfficial sources cited on this page
Continue with the same file
Each of these opens what the tool above produces. Use “Use in another tool” under the result to carry the file over — it moves from tab to tab inside your browser, never to a server.
Switched-off tools are not listed here: only what works right now.