Ghost CMS Blog Image Optimization means preparing each visual for its real job: feature image, image card, gallery item, screenshot, chart, author image, tag image, site image, newsletter image, social card, or theme-generated responsive image.
A good Ghost image is not just attractive. It should help readers understand the post, survive the active theme crop, load well, support metadata previews, and avoid copyright or privacy risk. Start by naming the image role, then prepare a delivery copy that fits the post, homepage card, gallery, newsletter, or social preview where it will appear.
What Ghost Images Need To Do
Ghost images need to serve readers in more than one place. A feature image may appear on the post page, homepage, tag archive, author archive, newsletter preview, and social card depending on the theme and settings. An image card belongs inside the post body. A gallery needs a consistent set of images, not one huge hero mixed with tiny thumbnails. A screenshot needs readable labels and private data removed.
Because Ghost themes control layout, there is no single feature image size that works for every publication. A clean source image still needs preview checks in the current theme, especially when the homepage uses cards, masonry layouts, carousels, or large post headers.
Feature Images, Image Cards, And Galleries Are Different
Feature image
Represents the post before the reader opens it and may feed homepage, archive, email, and social previews.
Image card
Appears inside the post body and should clarify the surrounding paragraph.
Gallery
Groups related images; Ghost supports galleries of up to 9 images and optimizes them responsively.
Theme image
Depends on package.json image sizes, img_url, srcset, and the active theme's crop choices.
Ghost CMS Image Role Decision Table
| Ghost image role | Where it appears | What it should communicate | Main risk | What to preview before publishing |
|---|---|---|---|---|
| Feature image | Post header, homepage cards, tag pages, author pages, newsletters, and social previews. | The core topic and promise of the article. | Theme crop hides the subject or the image misrepresents the post. | Post page, homepage card, mobile card, excerpt, X card, and Facebook card. |
| Image card | Inside the Ghost editor content flow. | A supporting example, photo, diagram, or visual explanation. | Decorative filler or oversized file that slows reading. | Desktop and mobile post body, caption, and alt text. |
| Gallery image | Gallery card inside the post. | A consistent visual set for a story, tutorial, portfolio, or travel/design article. | Mixed ratios, inconsistent crops, too many heavy images. | Gallery balance, mobile layout, captions, and image order. |
| Screenshot | Post body, tutorial, product update, or documentation article. | A specific interface or process detail. | Private data, tiny UI labels, or over-compressed text. | Mobile readability, sample data, redactions, and nearby explanation. |
| Chart or diagram | Educational or analytical post body. | A relationship, trend, process, or explanation. | Labels blur after compression or meaning exists only inside the image. | PNG clarity, alt text, caption, and written summary. |
| Author, tag, or publication image | Author pages, tag archives, site branding, and theme surfaces. | Identity or topic context for the publication. | Copied branding, weak contrast, or detail lost at small sizes. | Theme display, small-size legibility, and rights ownership. |
| X/Facebook/social card image | Post settings and external link previews. | A clear preview promise for off-site readers. | Wrong fallback image, stale metadata, or text-heavy crop. | Ghost metadata preview and platform card refresh after final edits. |
Responsive Images Help, But They Do Not Replace Image Judgment
Ghost can optimize and generate responsive image output, but the publisher still chooses the source, crop, format, caption, and context. Theme developers can define image sizes in package.json and use img_url with srcset so browsers receive suitable image variants. That helps performance, but it cannot fix a misleading feature image, a private screenshot, or a chart with labels too small to read.
For Ghost CMS image SEO and reader trust, place relevant images near relevant text, write descriptive alt text, add captions or credits when useful, and keep social metadata aligned with the article. Ghost's built-in metadata and social card fields are useful, but they work best when the image itself is specific and honest.
Privacy, Copyright, Captions, And Alt Text
Use images you created, licensed, or have permission to publish. Do not copy another Ghost publication's logo, cover style, or visual identity. Remove client names, emails, private analytics, login screens, account dashboards, API keys, invoices, internal documents, and confidential details from screenshots. Use sample data for dashboards and charts.
Alt text should describe the image's purpose for readers who cannot see it. Captions can add context, source credit, or disclosure. Do not use alt text as a keyword pile, and do not rely on an image to make a claim that the article text does not explain.
Related Ghost Image Guides
FAQs About Ghost CMS Blog Images
It is the process of preparing each Ghost image for its role, including feature images, image cards, galleries, screenshots, theme images, newsletters, and social previews.
A feature image represents the post in headers, cards, archives, newsletters, and previews. An image card appears inside the post body to support a specific section.
Ghost's editor guidance says uploaded images are optimized and made responsive, but publishers still need to start with clean, relevant, rights-safe images and preview the active theme.
No. Use a feature image when it honestly helps readers understand the post and works in the theme. A weak or misleading feature image can reduce trust.
Use images you created, licensed, or have permission to publish. Do not rely on credit alone, copy other publications, or include unauthorized logos and private screenshots.
