Documents
How to resize a screenshot without making the text unreadable
By ResizeFox · Published · Updated
A screenshot is useful only if its reader can identify the problem. Compressing an entire desktop into a small attachment often makes the relevant message too tiny to read. Start by deciding what the recipient actually needs to see, then reduce the image around that information.
Quick reference
| Use | Size or purpose | Note |
|---|---|---|
| Full desktop example | 2560 × 1440 px | Often includes unnecessary space |
| Relevant crop example | 1200 × 800 px | Crop in an image editor first |
| Half-size crop | 600 × 400 px | Text also becomes half as tall |
Step by step
- Capture the error and enough surrounding interface to explain where it happened. Keep an untouched copy for reference.
- Use ResizeFox’s Crop Image tool to remove unrelated windows. Redact private information in a separate editor with an opaque mark before opening the screenshot; ResizeFox does not provide redaction.
- Open the cropped file in the pixel resizer. Keep Maintain aspect ratio enabled and choose PNG output as a starting point for text-heavy content.
- Try one reduction, download the result and open it at normal viewing size. Read the smallest important text, including error codes and punctuation.
- If a support portal imposes a byte limit, compress only after checking readability. If the text becomes unclear, split the evidence into a contextual screenshot and a close-up when the portal permits multiple files.
Worked example: why cropping helps more than shrinking
Suppose the error panel occupies 1200 × 800 pixels inside a 2560 × 1440 desktop capture. Reducing the whole desktop to 640 pixels wide scales everything to one quarter of its original size. A 16-pixel-high character becomes roughly 4 pixels high, which is insufficient for reliable reading.
Cropping the panel first and keeping it 1200 pixels wide retains the original character size while removing irrelevant pixels. The result may still need compression, but you have not sacrificed text detail just to include empty desktop space. This example is a scale calculation, not a measured file-size saving.
Inspect the characters that carry the meaning
Check similar characters such as 0 and O, 1 and l, and punctuation in a URL or error code. A screenshot can look clean at a glance while losing the distinction that makes it useful. If the page allows text, paste the error message as text alongside the image.
JPG can introduce fringes around sharp text. PNG is a useful starting point, but it does not undo damage already present in a low-quality source. Re-capture the application if possible rather than converting a blurred JPG back to PNG and expecting the missing detail to return.
Check the attachment, not just the editor preview
Open the downloaded copy and view it at the size the recipient is likely to use. Confirm the right region was captured and the private details are no longer visible. Do not rely on a small email preview to confirm that a full-resolution attachment is unreadable; inspect the actual file.
See the tradeoffs yourself in the Image Compression Lab: compare text, gradients and transparent graphics with downloadable results.
Sources and further reading
Platform specifications and application rules can change. Refer to the current destination instructions; the worked calculations and preparation choices in this tutorial are not a guarantee of acceptance.