Why Substack Images Look Blurry, Cropped, or Too Heavy
When a newsletter creator uploads a beautiful post image and it later looks cropped in the social preview, soft in the email, or unreadable on a phone, the problem is usually not Substack alone. Most Substack image issues happen because the file was designed for one surface, exported at the wrong size, compressed too hard, or published without checking the email, web, mobile, and social previews.
This troubleshooting guide focuses on the real failure points: focal-point crop, mobile readability, heavy email images, tiny embedded text, and damaged chart or screenshot labels.
Why post preview images crop
A Substack post preview image has to fit preview cards, publication pages, app views, and social sharing contexts. Those surfaces may not show every edge of the original file. If the important subject sits near a corner, bottom caption, or extreme side, a crop can remove the point of the image.
Use a simple centered focal point for preview images. If the image contains words, keep them large and away from the edges. Do not rely on a long headline inside the image; the post title and subtitle already carry that information in the preview.
Why newsletter images look blurry on mobile
Mobile blur often starts with a mismatch between the source and the final reading size. A screenshot captured from a full desktop app may contain too much interface detail for a narrow email column. When it gets resized, labels and thin lines collapse. If the same file is also compressed heavily, the image can look soft even if it looked sharp in the editor.
For screenshots and charts, crop the image to the exact area that matters. Increase chart-label size before export. Use PNG for text-heavy graphics. Preview the post on a narrow screen before sending it to subscribers.
Why tiny text inside images is risky
Text embedded inside a newsletter image is not the same as text in the post body. It can shrink, blur, or become difficult for assistive technology depending on how it is used. If the words are essential, put the key point in the article text as well. Use the image to support the explanation, not to carry the entire argument.
Why large images make emails feel slow
A heavy image can make a newsletter feel crowded before the reader reaches the writing. Even when the image eventually loads, a large file can create blank space, delayed layout, or a visual pause that interrupts the inbox experience. The solution is not to destroy the image with extreme compression; it is to create a role-specific delivery copy.
Keep the original source file unchanged. Create a cropped upload copy for the exact role: logo, cover, preview image, header, chart, screenshot, or inline illustration. Then compress the delivery copy while checking that labels and artwork survive.
Diagnostic checklist
| Question | What it catches | Fix |
|---|---|---|
| Is this image for logo, cover, post body, or social preview? | One universal file being reused in mismatched surfaces. | Export a separate delivery copy for each role. |
| Is the focal point centered and simple? | Preview crops that remove the subject. | Move the key subject toward the center and remove edge-only text. |
| Is text readable on mobile? | Charts, screenshots, and captions that shrink too far. | Increase label size, crop tighter, or split the visual. |
| Did compression damage labels or screenshot text? | Artifacts, fuzziness, and broken chart lines. | Use PNG for text-heavy images and reduce compression strength. |
| Does the image work in email and web preview? | A file that looks good in the editor but fails after rendering. | Use Substack preview and send a test when layout matters. |
| Did you keep the original unchanged? | No way to rebuild after a bad crop or export. | Save the source image and publish only the delivery copy. |
Prepare logo and cover images separately
A publication logo has to remain identifiable at small sizes. A cover image can be more expressive, but it still needs a safe crop and strong contrast. A post preview image should explain one post, not carry the entire publication identity. Preparing these assets separately avoids a common Substack problem: the logo looks sharp, but the cover feels cramped, or the preview image crops away the topic.
FAQs
Preview images appear in multiple card and feed contexts. If the focal point sits near the edge or the image has important corner text, a preview crop can hide it.
The chart may have labels designed for desktop viewing. Increase label size, crop the chart, simplify the data view, and preview at mobile width.
No. Compression should reduce weight while preserving the visual purpose. If screenshot text, chart labels, or artwork become unclear, the delivery copy has gone too far.
