Publish release notes your users will actually read

Write release notes in markdown. Publish to a URL. Link from your app, your emails, or your support docs.

Release notes are not changelogs

Changelogs are for developers. Every commit, every PR, every technical detail. Release notes are for users: what's new, what changed, what to do next. They serve different audiences and need different formats.

Most teams write release notes in markdown but have no good place to publish them. You could paste them into a blog post (heavy), add them to your docs site (buried), or include them in an email (not linkable later). What you want is a clean page at a stable URL that you can link to from anywhere.

MDtoLink does exactly that. Write markdown. Publish. Share the link.

How it works

1. Write release notes in markdown

# v2.3 Release Notes

## New Features
- **Dark mode**: Toggle in Settings > Appearance
- **Export to CSV**: Available on all table views

## Changes
- Search now returns results in 200ms (was 800ms)
- File upload limit increased to 50MB

## Upgrade Notes
Run `npm update @yourapp/cli` to get the latest version.

Standard markdown. Use headings, lists, code blocks, whatever your users need to see.

2. Publish with a version slug

mdtolink publish release-notes-v2.3.md --slug v2.3

Each version gets its own URL. Your users can bookmark specific releases or view the latest.

3. Link from your app's update notification

// In your app's "What's New" dialog
const releaseNotesUrl = "https://mdtolink.com/@yourhandle/v2.3";

// Or with a custom domain (Publisher plan)
const releaseNotesUrl = "https://releases.yourapp.com/v2.3";

Drop the URL into your in-app notification, email template, or support page.

Why use MDtoLink for release notes?

Each version gets its own URL

Use different slugs per release. Link to specific versions from support tickets, emails, or your app.
Readers don't need accounts

No login wall. Your users click the link and see the release notes. That's it.
Custom domain support

On the Publisher plan, host release notes at releases.yourapp.com.
Archive of every release

Over time, you build a browsable history of release notes. Users can look back at any version.

Frequently Asked Questions

What's the difference between release notes and a changelog?

A changelog tracks every change for developers: commits, PRs, technical detail. Release notes summarize what matters for users: new features, behavior changes, upgrade steps. They serve different audiences. See our changelogs use case for the developer-facing side.

Can I have a separate URL for each version?

Yes. Use a different slug for each release: mdtolink publish release-v2.3.md --slug v2.3 and mdtolink publish release-v2.4.md --slug v2.4. Each gets its own permanent URL.

Can I link release notes from my app's UI?

Yes. The published URL works anywhere: in-app modals, notification banners, email templates, support docs. It's a standard HTTPS link that renders a clean page.

Do readers need an account to view release notes?

No. Published pages are public. Anyone with the link can read them. No login, no sign-up, no paywall.

Publish your next release notes in 30 seconds

Free to start. No credit card required.

Start Publishing Free Read the Docs

Looking for developer-facing changelogs? See Publish Changelogs. Or browse all use cases.