Turn release notes or a changelog into a LinkedIn carousel

Paste the link to a public release notes page below, for example a GitHub release or your product's changelog page. Slidler reads the page, uses its title as the cover and picks individual changes as slides, keeping the original wording. Delete issue numbers and minor fixes, keep the changes users will notice, then download a 1080×1350 PDF for LinkedIn or PNGs for Instagram. It's free and needs no account.

Step by step

Copy the link to one release, e.g. https://github.com/owner/repo/releases/tag/v2.0, or to your changelog entry. One version per carousel works best.
Paste it into the Link tab below. If the page needs a login or can't be read, copy the notes into the Text tab instead.
Choose 6–10 slides. Remove issue and pull request numbers like (#123), and rewrite the cover line as a hook such as “What's new in v2.0”.
Download the PDF, post it on LinkedIn with “Add a document”, and link the full release notes in the post text.

Make your carousel now (free, no sign-up)

Slides
Your handle

Example carousels made with Slidler

Browse all carousel examples →

FAQ

Which pages work?

Public pages that show the notes as normal text, such as GitHub releases or a plain changelog page. Pages that need a login or load the notes with scripts may come back empty; paste the text instead.

Will it pick the most important changes?

It picks the most informative sentences, not the most important features. Check every slide and swap in the changes your users care about; you can edit or delete any slide.

Why do issue numbers show up?

Slidler keeps the original wording, so references like (#8420) stay on the slide. Delete them in the editor under each slide.

Can my CI make the carousel on every release?

Yes. Slidler has a free public API and MCP server without a key that takes a URL or text. See slidler.com/llms.txt.