Most Ghost image problems come from the wrong source, role, crop, format, compression level, theme output, gallery mix, or preview setting, not from one missing magic image size.
If your Ghost feature image crop hides the subject in a mobile preview or Ghost social card, diagnose where it appears first. A blurry screenshot may be a source or compression issue. A slow page may come from oversized images, decorative GIFs, or a theme that does not request suitable responsive sizes.
Start With The Surface Where The Problem Appears
A cropped homepage card does not have the same cause as a blurry screenshot inside a tutorial. A stretched feature image usually means the asset is being forced into a layout it was not designed for. A slow article may have a feature image, gallery, or GIF that is heavier than the story needs, even if Ghost creates responsive versions.
Blur
Check source sharpness, screenshot scale, repeated compression, and whether the theme is enlarging a small file.
Crop
Check feature image subject placement, homepage card layout, tag pages, author pages, and social card metadata.
Stretch
Check whether a vertical image is being used as a wide feature image or publication cover.
Slow load
Check file weight, image count, GIF use, gallery size, and whether the theme outputs responsive sizes.
Ghost Image Problem Diagnosis Table
| Problem | Likely cause | Practical fix | What to preview | Reader trust / performance risk |
|---|---|---|---|---|
| Feature image looks cropped | The theme crops cards, homepages, tag pages, author pages, or social previews differently from the full image. | Use a wider crop with the subject away from edges and set custom social images if needed. | Post header, homepage card, archive card, X card, and Facebook card. | Readers may misunderstand the post before opening it. |
| Blog image looks blurry | Small source image, repeated compression, screenshot scaled too far, or theme enlargement. | Return to the original source and export a clean role-specific delivery copy. | Mobile and desktop post view at real reading width. | The article can feel careless or hard to trust. |
| Image looks stretched | The wrong aspect ratio is being forced into a feature image, card, gallery, or theme surface. | Crop from the original instead of stretching the export. | Theme card, post header, and gallery layout. | Stretched visuals look unprofessional and distract from the content. |
| Page feels slow | Oversized uploads, too many large gallery images, heavy GIFs, or theme output that does not request suitable sizes. | Compress the largest visible image first, reduce decorative images, and check theme srcset behavior. | Post page, mobile preview, newsletter preview, and image-heavy sections. | Readers may abandon the page before the content is useful. |
| Screenshot is unreadable | The capture contains too much interface detail or compression damages text and lines. | Crop to the relevant area, use PNG, remove private data, and summarize the key point in the text. | Mobile post body and caption context. | The image looks technical but fails to explain anything. |
| Gallery feels inconsistent | Mixed ratios, random crops, unrelated images, or too many heavy visuals. | Choose a consistent ratio and sequence; keep only images that belong together. | Gallery desktop and mobile layout. | The gallery may feel noisy or slow instead of editorial. |
| Social card shows the wrong image | Default metadata is being used, the custom social image is missing, or an external platform cached an older card. | Set metadata, X card, and Facebook card fields where needed, then refresh external previews after final edits. | Ghost social preview and external card tools. | Readers may see a mismatched title, excerpt, or image. |
Why Ghost Feature Images Crop Differently
Ghost stores the post data, but the theme decides how the feature image is displayed in many places. A homepage card may crop to a different shape than the post header. A tag archive may use another size. A custom theme may define image sizes in package.json and request them with img_url. That is why exact Ghost feature image dimensions are theme-dependent.
Why Oversized Images Can Still Be A Problem
Ghost's automatic optimization and responsive behavior help, but they do not make every upload a good choice. If the source is enormous, decorative, or repeated many times in a gallery, the reading experience can still suffer. Start with the largest visible image, usually the feature image or first large image card, then inspect screenshots, charts, and gallery items.
External Images And Custom Storage Need Extra Checks
Images inserted by URL, served by a custom storage adapter, or output by a custom theme may behave differently from ordinary Ghost-hosted images in the editor. If a post relies on external images, preview loading, sizing, alt text, and fallback behavior carefully. Do not assume the same responsive processing applies everywhere.
Diagnostic Checklist
- Is the original image sharp before upload?
- Is the image role feature image, image card, gallery, screenshot, chart, or social card?
- Does the current Ghost theme crop feature images in cards or homepages?
- Is the subject too close to the edge?
- Is the file oversized for its role?
- Did compression damage important details?
- Is the screenshot readable on mobile?
- Does the gallery use consistent ratios?
- Does the image need a caption or credit?
- Is useful alt text present?
- Is the image rights-safe?
- Does the image expose private data?
- Does the image match the article topic?
Where To Go Next
FAQs About Ghost Image Problems
Your theme may crop feature images differently in headers, homepages, archives, and social cards. Re-crop with safe space around the subject and preview the active theme.
The source may be too small, the image may have been compressed too many times, or the theme may be displaying it larger than intended.
The screenshot may include too much interface detail. Crop to the relevant panel, use PNG, enlarge labels when possible, and explain the key point in nearby text.
Ghost may be using fallback metadata, or the social platform may have cached an older preview. Check the post metadata, X card, and Facebook card fields, then refresh the external preview.
Yes. Responsive output helps, but huge source images, heavy GIFs, and overloaded galleries can still hurt the reading experience.
