Four tools that do the same job in four different ways. Which one fits depends on whether you have a GPU, how long your clip is, and whether you are willing to install anything.
| UpgoLAB | Upscayl | Video2X | Topaz Video AI | |
|---|---|---|---|---|
| Runs in browser | Yes | No, desktop | No, desktop | No, desktop |
| Needs local GPU | No | Yes | Yes, Vulkan | Yes, strong GPU |
| Free tier | Yes, unlimited during launch | Yes, open source | Yes, open source | No |
| Photo support | Yes, up to 4 MP | Yes | No | Yes |
| Video support | Yes, up to 30 s | No | Yes, unlimited length | Yes, unlimited length |
| Content-specific presets | 8 modes | Several models | No | Some |
| Watermark on free | No | No | No | n/a |
| Works on phone | Yes | No | No | No |
| Setup time | None | Install + model download | Install + build | Install + licence |
Runs on cloud RTX 5090/3090 GPUs, so the device you are holding does not matter. That is the whole point: a phone photo of a grandparent, or a 20-second clip pulled from a messaging app, can be fixed without buying a graphics card.
The constraint is real and worth stating plainly: 30 seconds per video file, 4 MP per photo. For longer files you have to split first (commands below).
Eight presets exist because content degrades differently. Compression blocks need a different treatment than sensor grain, and anime line art needs the opposite of what night footage needs.
Open source, wraps Real-ESRGAN and similar models. Excellent for photos if you already own a capable GPU. No video support at all. A common choice for people restoring scanned prints.
Free and open source, handles video of any length and also does frame interpolation. Requires a Vulkan-capable GPU and some patience with the build. The documentation is good; the setup is not trivial for non-technical users.
Best-in-class for long-form professional work, with model choice per clip and mature handling of motion. The reason to avoid it is cost, and the reason to consider it is a 40-minute timeline you need to deliver today.
Most guides say enlarge first. That makes the model learn the compression blocks and enlarge them too. The sequence that holds up:
Past roughly 2x the model switches from reconstructing to inventing. Faces go waxy and small text turns into strokes that look like letters but are not.
Cut at keyframes so the source is not re-encoded:
ffmpeg -ss 00:01:12 -to 00:01:38 -i input.mp4 -c copy segment.mp4
Batch split:
ffmpeg -i input.mp4 -c copy -f segment -segment_time 30 -reset_timestamps 1 seg-%03d.mp4
Rejoin without a second encode:
printf "file '%s'\n" seg-*.mp4 > list.txt
ffmpeg -f concat -safe 0 -i list.txt -c copy output.mp4
Each of these is the model output, not a marketing render:
Each preset targets a different kind of damage. These are the same photos the tool ships as demo material:
| 01 Natural | ![]() |
| 02 Ultra Crisp | ![]() |
| 03 Social Denoise | ![]() |
| 04 Portrait Studio | ![]() |
| 05 Anime 2D | ![]() |
| 06 Cinema Vivid | ![]() |
| 07 Clear Reality | ![]() |
| 08 True Texture | ![]() |
UpgoLAB runs entirely in the browser with no install and no local GPU. Photos up to 4 MP, video clips up to 30 seconds, enlarging to 2K or 4K. Free during launch, no watermark.
For short clips, UpgoLAB is free and needs no GPU. For long video on your own hardware, Video2X is free and open source but needs a Vulkan GPU. Neither matches Topaz on long-form work, but both cover the common case.
Yes, with a cloud tool. UpgoLAB processes on cloud GPUs, so any browser works including phones. The tradeoff is a 30 second cap per file.
At most 2x per axis. A 540p source at 2x lands at 1080p — enough for anything watched on a screen. Pushing 4K from a 480p source produces a larger file with the same real information.
Usually one of three things: denoising after enlarging (blocks already amplified), a single model used for both night grain and line art (opposite requirements), or judging quality at fit-to-window instead of 100% on an edge.