Increase Image Resolution — Free, Fast & Private
Resolution problems are arithmetic problems, so start with the numbers. Prints want about 300 pixels per inch. Screens want whatever the layout says, plus double for high-density displays. Multiply the size you need by the density it wants, and you have a pixel target; your file either meets it or it does not. When it does not, you have two honest options: print smaller, or create real pixels — and creating them well is precisely what a server-grade reconstruction model is for. What never works is the DPI-metadata trick: relabelling 72 DPI as 300 DPI moves numbers in a header while the print stays exactly as coarse as before.
4x each side is more headroom than it sounds. A 900x1200 web export becomes 3600x4800 — an 8x10" print at 300 DPI with margin to spare. A 2000x1333 camera crop becomes 8000x5332, poster-sized. That is why the intake cap of 4 megapixels rarely pinches: sources above it are almost always print-ready already, and the cap is what keeps the 16x output inside what a GPU can reconstruct with genuine care rather than speed-blur.
Prepare on your device, reconstruct on ours, finish on yours. Crop to the final composition first with the on-device crop tool — pixels spent on scenery you will trim are pixels wasted. Then one enhancement run, encrypted in, deleted on completion. Then any format conversion or compression for delivery happens back on your device. Only the middle step ever sees our server.
The cost, in plain numbers. Each run spends one cloud run from your Pro allowance (150 a month on Monthly, 200 on Annual) and one of the month’s 10 HD runs — both meters are shown before every run and on your account page. Refused and failed runs charge neither. And when the job is screen-bound and ordinary, the free on-device upscaler does it with no upload at all.


