Identify what leaves the device
A browser service generally requires an image to be transmitted for processing. A desktop application may offer local features, cloud features or both. Inspect the specific mode and current documentation rather than assuming that installation means every operation stays local. Confirm that the image owner permits the intended processing. For confidential or sensitive material, follow the applicable organizational requirements; this guide is not a substitute for a privacy or legal assessment.
Separate convenience from permission
Fast access from several computers can be useful, but convenience does not supply permission to upload client work. Conversely, a local route can still create copies, caches or shared-folder exposure that require care. Keep originals and exports in appropriate storage, avoid unnecessary sharing and record the workflow in the project brief. Do not send personal image metadata or filenames to site analytics. Our sizing calculator needs only numbers and does not upload your images.
A studio decision example
A fictional studio has two jobs: public artwork owned by the artist and a private family portrait commissioned for a gift. The first may permit an approved cloud workflow; the second may require additional owner agreement or a local route. Use separate decisions rather than one default for every file. Check the exact product mode, account terms and deletion or retention controls before transferring the private image. Do not infer those guarantees from marketing phrases alone.
Evaluate the remaining tradeoff
Once a route is permitted, compare hardware needs, transfer time, consistency and correction effort. Keep costs and data handling separate from output quality; a private workflow can still produce an unsuitable image. Judge the final dimensions and fidelity against the same brief. If neither route is appropriate, obtain a better source or use a smaller print. The correct answer can be to avoid processing rather than to force an image through the most convenient service.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Let's Enhance print-preparation help (September 16, 2026) — Merchant documentation · help.letsenhance.io · Merchant-controlled · checked 2026-09-25
- Upscayl official product and desktop/cloud distinction — Merchant documentation · upscayl.org · Merchant-controlled · checked 2026-09-25
- Topaz Gigapixel current product description — Merchant documentation · topazlabs.com · Merchant-controlled · checked 2026-09-25