Quick answer: A changelog is written for users who already care; a changelog visual is written for users who do not know anything changed yet. The text version lives in the release notes. The visual version turns the same updates into cards that survive a feed.

The difference between notes and visuals

The release note says:

Added bulk export, improved the CSV import, and fixed timezone handling on scheduled items.

The visual says:

  • One headline card: "Two updates this week."
  • One feature card: "Export the whole workspace to CSV in one click."
  • One improvement card: "Import now handles ten thousand rows."
  • One closing card: "Live today."

The fixes, the internal names, and the version number stay in the text. The release-note writing guide covers the full text version; this guide covers the visual layer.

The card types

The changelog maps cleanly onto a small set of layouts:

  1. The hero. The release name, the date, and one sentence.
  2. The feature card. The single new thing, with one screen or one icon.
  3. The steps card. A numbered flow for the new workflow.
  4. The comparison card. Before and after, or old plan versus new plan.
  5. The metric card. A factual improvement: time saved, limits raised, or pages added.
  6. The list card. The full monthly summary, as a compact set of bullets.

What to include and what to cut

Include:

  • What changed, in the user's language.
  • What it lets them do now.
  • The name of the feature as it appears in the product.
  • One screenshot per major feature.

Cut:

  • Internal tickets and jargon.
  • Bug fixes the user will never notice.
  • Dependency bumps.
  • More than three changes on a single card.

If a release has eight changes, the list card summarizes them and the two biggest changes get their own cards.

The hierarchy on a single card

  • The category label is small: "New · Export."
  • The feature name is the headline.
  • The outcome sentence is the subtitle.
  • The screenshot or icon fills the remaining space.
  • The logo and the handle are small and consistent.

The copy rules

  • Name the feature, then name the outcome: "Bulk export — get the entire table in one click."
  • Keep the sentence on the card under twelve words.
  • Write the rest of the explanation in the caption.
  • Use the same tense and the same naming as the product.

The batch workflow

  1. Write the release notes in text first, as the source of truth.
  2. Mark the two or three updates worth a card.
  3. Capture the screenshot for each.
  4. Generate the hero, the feature cards, and the list card as one set.
  5. Resize the set to the feed and the story sizes.
  6. Pair each card with a short caption and the link to the notes.
  7. Schedule the series across the launch week; the scheduling guide covers the cadence.

This is the same repurposing logic as one announcement into a week of posts and the batch content workflow.

Monthly and weekly formats

  • Weekly changelogs. One hero and one or two cards, posted on the same day each week.
  • Monthly roundups. A list card with six to eight items, plus one feature card for the headline update.
  • Major releases. A full mini-campaign: hero, two features, a comparison, and a release email.

The rhythm matters more than the design. A recurring changelog series trains the audience to expect improvement.

A tool path for teams with no designer

A single paragraph of release notes is enough input for an AI design tool to produce the card set. The tool splits the notes into the card types, assigns the screenshots, and lays them out at the feed and story sizes. Neatico does this for social campaigns from a product description: paste the changelog, get the eight-card set and the captions.

What to avoid

  • Copying the changelog verbatim onto a card; paragraphs are not graphics.
  • Inventing percentages like "10× faster" unless the benchmark exists.
  • Showing a screenshot of the internal admin view.
  • Designing each update in a different style; the series must look like a series.
  • Posting the changelog without a caption; the visual starts the story, the caption finishes it.
  • Forgetting to announce the feature inside the product as well as on social.

Frequently asked questions

How many changelog cards per release? One hero plus one card per major change, capped at four. Small fixes go in a list card or stay in the text notes.

Should bug fixes get visuals? Only the ones users will feel, such as a reported crash or a much faster workflow. Everything else stays in the written changelog.

What size should a changelog card be? The 1:1 (1080×1080) or 4:5 (1080×1350) feed card is the default; the 9:16 story version reuses the same content for a deadline-free countdown. The size cheat sheet has the full list.

Can the changelog visual replace the text notes? No — the text is the searchable, linkable, permanent record. The visual is the distribution layer on top.

Write the notes first, pick the changes worth an image, and let the series build a visible record of momentum. Shipping quietly is the most common mistake.

Related guide: the screenshot marketing guide.