Skip to content

Changelog formatter

Paste one change per line, start a line with added, changed, fixed, removed, deprecated or security to file it, and copy the release notes in the format you need.

  • Runs in your browser
  • Nothing is uploaded
  • Free, no sign-up
  • method v1.0.0
  • Updated Oct 2026

Input

For example 1.4.0. Leave it empty for an unreleased entry.

Year, month and day: 2026-10-08.

One change per line. Start a line with added:, changed:, fixed:, removed:, deprecated: or security: to file it. Lines without a prefix go under Changed.

Up to 20,000 characters.

Updates as you type · nothing leaves this page

Result

Paste your changes

Write one change per line, or load an example to see the release notes in each format.

Turns a list of changes into release notes in the Keep a Changelog structure, as Markdown for your site, as a blog or social post, or as an email, and lists what is missing from the entry. For founders and small teams who ship often and write release notes by hand.

How to use it

  1. Enter the version and the release date, or leave both empty for an unreleased entry.
  2. Write one change per line. Start a line with added:, changed:, fixed:, removed:, deprecated: or security: to file it.
  3. Choose the format: Markdown, a post or an email.
  4. Check the findings, then copy the release notes or download them as a file.

How Reavlo tests this

The notes are formatted in your browser from the lines you paste. Nothing is uploaded and nothing is stored.

Reading the lines. Each non-empty line is one change. A leading bullet (- or *) is dropped. If the line starts with a known category word and a colon, the change is filed under that category; the words add, new, feat, update, improve, fix, bugfix and the six category names are understood. Any other word before a colon is part of your sentence, and a line with no category goes under Changed. Up to 200 lines are used.

Structure. Categories follow Keep a Changelog 1.1.0: Added, Changed, Deprecated, Removed, Fixed and Security, in that order, with empty groups left out. The entry is titled [version] - date, or [Unreleased] when there is no version.

Formats. The three formats use the same lines. Markdown uses headings and lists, the post leads with a plain title and the email adds a subject line. The title and the one-line introduction are chosen from templates by what the entry holds, for example an entry made only of fixes gets its own introduction.

Checks. No changes is critical. A missing version, a missing date and an entry longer than 140 characters are warnings. Lines without a category are noted.

Limits. The tool does not judge whether a change matters to readers or whether it is accurate. It does not group related lines or rewrite them: your wording is kept as typed.

Questions

Is what I paste uploaded?

No. The release notes are built in your browser. Nothing you paste is sent to a server or stored, which is also why this tool has no share link.

What is Keep a Changelog?

It is a widely used way to write a changelog: one entry per version, newest first, with changes grouped as Added, Changed, Deprecated, Removed, Fixed and Security. This tool formats one entry; you paste it above the earlier ones in your file.

What happens to a line with no category?

It goes under Changed, and the tool tells you how many lines it filed that way. Start the line with added: or fixed: when it belongs somewhere else.

Can I use it for the first release?

Yes. Write every line as added: and set the version, for example 1.0.0, and the date. Leave both empty to produce an unreleased entry.

Why are there three formats?

The same changes are read in different places. Markdown suits a changelog file or a docs page, the post suits an announcement, and the email adds a subject line for customers who want to be told.