Download the Image, Not the Preview Screenshot

The picture in a generator’s result panel is not necessarily the whole picture. A preview can fill an attractive card by cropping the edges, while the original file remains a wider composition. Saving a screenshot of that card can turn a display choice into a permanent change to your artwork.

That difference was visible in this kite illustration. The downloaded image was a 1280 × 720 JPEG. A capture of the result image as displayed on the page was 716 × 681 pixels and showed a much narrower part of the composition. It was the same generated output, not a second version with a different crop instruction.

The practical fix was to save the original result and check that file before making publishing copies. No regeneration was needed.

Make the edit, then separate the files

The source was an AI-created cut-paper illustration: a blue kite above ochre hills, with a cream ribbon tail. I used the reference-image editing workflow in [Grok Image 2.0](https://grokimage20.com/) to change the tail to terracotta red while retaining the landscape composition.

The run used Standard quality, a 16:9 frame and a 1K request. This session required the form’s missing resolution field to be supplied; the result file was 1280 × 720 rather than a square 1024-pixel image.

This was the complete submitted edit instruction:

Edit the uploaded cut-paper kite illustration. Change only the short cream ribbon tail of the blue kite to a vivid terracotta red ribbon tail. Keep the blue diamond kite, dark string, three ochre hills, cream sky, cut-paper edge style, paper texture and landscape composition. Do not add a second kite or change the number of hills. No text, logos, watermark or interface.

The returned file shows the blue kite, red ribbon shapes, cream sky and ochre hills. The file-delivery question begins after that result exists. Rewriting the prompt would not explain why a page preview looks different from the original file.

Keep the input, generated result and any publishing export separate. Otherwise, a small screenshot can be mistaken for the master simply because it has the most recent filename.

What the preview changed

The result panel used a tall image box with a cover-style fit. That makes the image fill the available space, but the sides of a wide composition can fall outside the visible box.

In this browser session, the image element was about 716 CSS pixels wide and 680 high. Its underlying image was still 1280 × 720. A CSS-scale element screenshot produced a 716 × 681 PNG; the extra pixel reflects the captured element boundary, not extra image detail.

Those measurements describe this page and viewport, not a fixed screenshot size every reader will get. Browser zoom, window dimensions and capture method can all change the saved screenshot. Here, the important observation is simpler: the near-square preview had already hidden parts of the landscape.

A PNG screenshot is not automatically a better source than a JPEG download. The format tells you how the captured pixels are stored. It does not tell you whether the frame is complete or whether the image was reduced before capture.

Open the original result before saving

The result page offered “Open full image” and “Open / save,” both pointing to the same original JPEG. Use that original-image route rather than capturing the result card.

Once the image opens, save the file itself. Then open the saved file independently of the generator page and check its dimensions. For this case, the full file should be landscape and 1280 × 720, with more of the hills and surrounding sky visible than in the tall preview.

Do not judge this only by how large the picture looks on screen. An image viewer can fit a large file into a small window, and a browser can enlarge a small file. Pixel dimensions and complete framing are more informative than apparent display size.

Also make sure the saved item is an image rather than a webpage, shortcut or screenshot. A useful filename can include the subject and role, such as “kite-red-tail-master.jpg.” The role matters more than an impressive-sounding quality label.

Make a publishing copy from the master

Once the original is secure, create the version needed for the article, newsletter or social card. This is the point at which cropping becomes a deliberate design decision.

If a platform wants a square image, choose what can be removed from the sides without weakening the composition. If the kite or its tail becomes cramped, consider a different placement or a padded layout instead of accepting the generator panel’s automatic crop.

Keep that square export alongside the landscape master, not over it. A later request for a wide banner should not require enlarging a screenshot or reconstructing parts of the original composition.

File size is a separate decision. Compress a publishing copy to meet the destination’s limit and inspect it again. A smaller file can be perfectly suitable if the subject, edges and paper texture still work at the intended display size. There is no advantage in preserving excess bytes that the platform will immediately recompress.

If a file still looks wrong

First compare it with the opened original at the same framing. If one file is square and the other is wide, investigate the crop or capture path before questioning the generation.

If the dimensions match but the image appears softer, inspect the export settings and whether it has been repeatedly resized. Do not add sharpening before checking whether the correct master was used.

If the original itself has the wrong tail colour or an unwanted object, that is a separate image-editing decision. File handling can preserve the output you received; it cannot correct what was generated.

The distinction keeps the next action small. A preview crop needs a better save route. An unsuitable publishing crop needs a new export. A genuinely wrong image may need another edit.

Check the actual file you will upload

• The master came from the original-image link, not a screenshot.
• Its dimensions and aspect ratio match the downloaded result.
• The full composition has been inspected outside the result panel.
• Publishing crops were made intentionally and saved separately.
• Compression meets the destination’s file limit without obscuring important detail.
• The file selected for upload is the intended export, not the input or an earlier screenshot.