Create structured changelog entries following Keep a Changelog format with version, date, and change categories.
This tool assembles a changelog entry in Keep a Changelog format. You supply a version number, a release date, and change descriptions assigned to categories; it returns a block with a `## [1.2.0] - 2026-08-16` heading and `###` category headings, ready to paste into CHANGELOG.md. Everything runs in the browser; nothing you type is uploaded. The usual mistake is loose categorization: the six categories are fixed and narrower than everyday usage, so a bug fix belongs under Fixed, not Changed, and a still-present but superseded feature under Deprecated, not Removed. The date is the release date in ISO 8601 form, not today's date.
A concrete input and expected output from the current implementation.
Input
Version: 1.2.0 Date: 2026-08-16 Added - Support for dark mode - Export to CSV Fixed - Saved dates displayed one day early
Expected output
## [1.2.0] - 2026-08-16 ### Added - Support for dark mode - Export to CSV ### Fixed - Saved dates displayed one day early
Each entered item becomes a `- ` bullet under its category heading, and only the categories you used appear, in the canonical template order (Added, Changed, Deprecated, Removed, Fixed, Security), so Fixed follows Added. The heading joins the version and the ISO date in the spec's `## [version] - date` form.
Every item lands under one of the format's six headings: Added, Changed, Deprecated, Removed, Fixed, Security. The output lists the sections you used in the canonical template order, with items under each heading kept in the order you entered them. Sections you left empty do not appear at all.
The entry opens with a level-2 heading joining the version and the date: `## [1.2.0] - 2026-08-16`. The date is the release date, and the format requires ISO 8601 order, year-month-day; an entry dated 16-08-2026 or Aug 16, 2026 would be out of spec. The heading anchors everything below it, so it is the first thing to check before pasting.
No. The tool outputs the entry for one release: the heading, category sections, and bullets. The surrounding scaffolding stays your responsibility: the `# Changelog` title, the paragraph crediting Keep a Changelog and Semantic Versioning, the bottom comparison links such as `[1.2.0]: https://github.com/you/repo/compare/v1.1.0...v1.2.0`, and all older releases. Paste the block directly under the title paragraph, above the previous version.
No, categorization is your call; the tool formats what you assign. When in doubt, use the spec's definitions: Added is new behavior, Changed is altered existing behavior, Deprecated is still present but on the way out, Removed is gone, Fixed is bug fixes, and Security is vulnerabilities. If a change fits two categories, pick the more specific one and mention the other in the item text.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.