Thumbnails, previews and originals: checking AI asset quality

Check the downloaded file before judging sharpness

A soft image on the canvas does not necessarily mean generation resolution is low. Open the full preview, wait for the clear resource, then download the actual file and inspect its pixel dimensions. A canvas screenshot is not a substitute for the original file.

Thumbnails help locate assets, previews help inspect content, and original files support detailed review. They may represent the same result at different sizes or compression levels. A preview can show a loaded small image before switching to a clearer resource.

Display size, import size and output settings are separate

The asset-size slider changes canvas arrangement, while preview zoom changes viewing scale. Neither adds file pixels. Generated output dimensions depend on the model and parameters; asking for a larger resolution in the prompt does not replace the output setting.

The image import budget is 20,250,000 total pixels and an 8192px longest edge. Exceeding either limit requires choosing to resize for upload or cancel. For example, 6000 x 4000 contains 24,000,000 pixels and needs resizing despite fitting the edge limit. This is an input limit, not a promised generation resolution.

After choosing to resize, the workflow receives the processed file. Keep the local original and check that small text remains readable. AI upscaling can invent textures, so larger width and height alone do not establish real detail.

Check files before delivery

1. Open the full preview and confirm that this is the final version.
2. Save the actual file through the download action and open it in a local viewer.
3. Check dimensions, format and any required alpha channel. A checkerboard in the picture does not prove transparency.
4. Check readability at the intended display size, then enlarge to inspect text, logos, outlines and repeated textures.
5. Archive inputs, key settings and final files together instead of retaining only screenshots or media links.

Common problems: blur, loading failures and wrong versions

• The canvas looks soft but the download is clear: the display resources differ. Review the downloaded file; this alone does not require another generation.
• The downloaded file is also soft: check whether the input was resized, whether output resolution is sufficient, and whether the generated details themselves are wrong.
• Preview or download fails: check the network, task completion and whether the resource is still accessible. Another generation will not repair an old link.
• The download is the wrong version: inspect the corresponding results individually instead of identifying the final version from similar thumbnails.

A video poster cannot establish clip quality

A sharp poster does not establish good motion, bitrate or audio throughout a video. Download and play the whole file, inspect action, light changes and sound, then preview it on the destination platform to check recompression.

Record the timestamp of each issue. A sharp frame followed by deformation is a content problem; stuttering playback or an inaccessible resource calls for loading checks first. These problems need different remedies.

Browser history is not a permanent file library

Local media used for generation is uploaded, and results return as remote media URLs. Browser history stores associated records. Seeing a history entry does not mean the file has been downloaded to your device or that the remote URL will remain available permanently.

History currently defaults to seven days of retention, up to 80 displayed entries and up to 120 stored entries per user. Clearing browser site data can also remove local records. Download approved originals, references and finished files into your own project folder instead of using history as a long-term backup.