Do not begin with the whole folder
A folder may contain scans, screenshots, photographs and illustrations with very different weaknesses. Group files by source type and intended output. Choose representative samples, including a difficult one. Establish crop, target dimensions and fidelity checks before processing the rest. This reduces the risk of repeating an unsuitable setting across many images. It also gives you a realistic view of correction effort rather than measuring only the time spent waiting for processing.
Keep a minimal ledger
For each file, record the original name, required dimensions, chosen processing route, output name and review status. Use separate states for processed and approved. Mark failures and unknowns explicitly. A batch can finish successfully from the software’s perspective while some images remain unsuitable for print. Keep the approved delivery folder separate so an unreviewed file cannot slip into a printer upload merely because it sits next to accepted outputs.
A mixed-collection example
A fictional twenty-image collection includes twelve modern photos, five scans and three illustrations. Do not infer that a good modern-photo sample approves the scans or artwork. Prove a representative file from each group and inspect the difficult signature or face cases individually. If one group consistently changes important detail, use another route or a smaller print for that group. The desired outcome is twenty suitable decisions, not twenty identical processing histories.
Budget for exceptions
Reserve credits, time and proof costs for rejected candidates and changed briefs. Check current batch and plan limits in the service rather than relying on an old interface tutorial. Avoid repeated processing of the same derivative; return to the controlled source when changing a material setting. After delivery, keep the ledger and originals according to your retention needs. No software completion badge substitutes for a reviewer accepting the exact final files.
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
- Let's Enhance current pricing; conflicting output limits retained — Merchant documentation · letsenhance.io · Merchant-controlled · checked 2026-09-25