AI Image Resolution: Check the Download, Not the Preview
Calculate required pixels, inspect the downloaded file, and separate true detail from an enlarged preview before using AI imagery in print or campaigns.
The short answer
Set the final pixel requirement from the destination, then inspect the downloaded file's dimensions and detail at 100%. A sharp in-app preview does not guarantee a large export, and upscaling can improve presentation without recreating factual detail that was never generated.
Resolution is the relationship between pixel dimensions, crop, and output size. File size alone does not prove quality, and a high pixel count does not repair distorted faces, labels, or objects.
Define the input and destination
- Final pixel dimensions or print size
- Expected crop
- Viewing distance
- Compression and file-format requirements
- Whether exact text, faces, or product detail must survive
Generation becomes easier to review when the intended destination is known in advance. Define what must remain exact, what the model may invent, and what another deterministic tool should add later. Exact words, prices, dates, logos, and regulated claims should not depend on generated pixels.
A practical workflow
- Step 1: Define the delivery size.
- Step 2: Download the original export.
- Step 3: Check pixel width and height.
- Step 4: Inspect edges and small details at 100%.
- Step 5: Upscale only after selecting and correcting the source.
Use FakeIt when a photo-led preset matches the task. Start with the photo-to-AI workflow guide when identity is the anchor, or compare generation with targeted editing when only part of the source needs to change.
Run a three-file production test
Use a strong input, an ordinary input, and a difficult input with the same task. Download each result rather than judging the in-app preview. This exposes repeatability, edge cases, real credit use, and the amount of manual review required.
- Record usable outputs rather than total generations
- Keep the crop and task constant
- Note failures that repeat across all three inputs
- Estimate correction time as part of cost
- Choose the workflow that fails predictably
A single impressive output demonstrates possibility. A small controlled batch demonstrates whether the workflow is dependable enough for a profile set, campaign, catalogue, or recurring content series.
Common failure modes
- Saving a screenshot of the preview
- Confusing DPI metadata with real pixels
- Upscaling before fixing artifacts
- Recompressing the same JPEG repeatedly
Do not keep an attractive error because it took time to produce. Once the image leaves the editor, viewers cannot see the prompt or the compromises; they see a representation of a person, product, place, or event that may appear factual.
Separate generation from deterministic finishing
Use generation for the parts that benefit from visual invention: scene, style, lighting direction, atmosphere, and broad composition. Move exact content into a deterministic editor after the generated pixels are approved. This includes logos, prices, dates, captions, legal copy, dimensions, and product labels.
Keep an editable master with safe margins and separate text or brand layers. That makes correction cheaper, creates cleaner alternate crops, and prevents a minor copy change from forcing the whole image through generation again.
- Approve the visual before adding copy
- Keep exact assets on separate layers
- Export destination-specific crops from the master
- Archive the approved version rather than the latest experiment
Full-size review checklist
- Are pixel dimensions sufficient after cropping?
- Do small details remain coherent?
- Is compression visible in gradients or edges?
- Does the destination accept the format and byte size?
Review at the real destination size and at 100%. Inspect faces, hands, repeated objects, edges, reflections, labels, jewelry, clothing, product parts, and generated text. Then view the crop on both a bright and dark screen when contrast matters.
Privacy, rights, and records
Control photo access with Apple’s current app tracking and permission guidance, and review each service’s current retention and model-training terms. For business assets, the U.S. Copyright Office AI initiative is a primary starting point for current U.S. copyright work.
- Use source material you control
- Get permission from recognizable people
- Keep the source, prompt or preset, edits, and approval together
- Do not assume a clean export resolves copyright, trademark, publicity, or disclosure questions
How FakeIt fits
FakeIt is designed for fast photo-led creation on iPhone. Choose a preset, use an image you control, compare the result with the source, and export the reviewed file. Use a prompt-first generator for open-ended invention and a deterministic editor for exact layout, copy, labels, and logos.
Keep the source and reviewed export together until the asset is approved in its final destination, where crop, compression, and surrounding copy can change the judgment.
Frequently Asked Questions
How many pixels do I need for print?
Multiply the intended inches by the printer's requested pixels per inch. For example, 8 inches at 300 PPI needs 2,400 pixels along that dimension before cropping.
Does AI upscaling add real detail?
It predicts plausible detail. It can improve appearance, but it cannot verify a face, label, texture, or product feature that was missing.
Is PNG always higher quality than JPEG?
PNG avoids JPEG loss but can be much larger. Use PNG for transparency or sharp graphics and a well-compressed JPEG for photographic images when appropriate.
Why is my downloaded image smaller than the preview?
The interface may display a scaled preview while the plan limits exports. Check dimensions and plan terms before committing to a workflow.
Should I disclose an AI-generated image?
Disclose it when viewers could be misled about a real person, event, product, place, credential, or result, and follow the current rules of the destination platform.
What should I save after generation?
Keep the reviewed master, source image, intended use, and enough workflow information to reproduce or audit a material asset.
Your next step
Choose one real destination and write four lines: required subject, crop, allowed changes, and protected details. Generate a small test set in FakeIt, inspect the downloads, and keep only the output that survives the checklist.