Bulk CSV export
Export filtered feedback with votes and customer context.
Turn shipped work into release notes people can scan, subscribe to and find later. Publish once in ProductLift, then show the same updates on WordPress, a hosted page and inside your product.
14-day free trial. No credit card required.
Changelog page
Product updates
New features, improvements and fixes
Bulk CSV export
Export filtered feedback with votes and customer context.
Faster roadmap filters
Find plans by status, category and target date.
Signed WordPress SSO
Improved session handling for embedded portals.
[productlift_embed tab="changelog"]Trusted by 6,000+ product teams
Teams use ProductLift to turn completed work into updates customers can discover, follow and understand.
4.8
on G2
4.9
on Capterra
4.6
on Trustpilot
The public update history
Write a short update or a complete release story with headings, lists, links, video and images. Readers can browse by date and category instead of digging through announcements scattered across blog posts and emails.
Create changelog entry
Ready for review
Title
Category
Release note
Export the feedback you are viewing
Filters, votes and customer context now travel with the CSV.
Release audience
Who should hear about this?
Changelog subscribers
1,284 people
Voters on linked requests
128 people
Inside the product
What’s New widget
Close the communication gap
A public changelog is useful even when nobody subscribes. Notifications make it more valuable by bringing the relevant update to the people who asked for it.
Notify changelog subscribers
Send a release email to the audience following your updates.
Notify voters on shipped requests
Link completed feedback or roadmap items so the original voters see the outcome.
Manage and export subscribers
Search the subscriber list and export it as CSV when your team needs the record.
Keep the message localized
Use the subscriber locale for translated release notes and notifications.
Reuse the work you already did
Start with a completed feedback or roadmap item when the customer context matters. Start from commit history or a raw changelog.txt when the release is engineering-led. Either way, edit the Git2Log draft before it becomes the public announcement.
Git2Log draft
3 commits selected
Faster, more complete CSV exports
Export the current feedback view with filters, segments and customer context. Large exports now finish faster too.
Review, add screenshots and choose the audience before publishing.
Beyond the WordPress page
The WordPress changelog gives every update a permanent home. The What’s New widget brings the same entries into the product, where active users are more likely to see them.
Show an unread update dot, open the latest entries from your navigation and let the reader dismiss what they have seen. Use the JavaScript SDK or embed so the release team still publishes from one place.
Bulk CSV export
Export filtered feedback with vote and customer context.
The update remains available on WordPress after the in-app prompt is dismissed.
Try the real changelog
Browse entries, categories and the subscription experience. This is the same hosted changelog you can place inside WordPress.
Live changelog demo
Open full screenMake every update useful
ProductLift handles the publishing and distribution. Your note still needs to tell the reader what changed, why it matters and what to do next.
Use the examples and templates in our guide to writing release notes people actually read.
Make sure it fits
ProductLift publishes your own features, fixes and announcements. If you only need to read WordPress core or a third-party plugin history, its release archive is the better destination.
Create a public history for features, fixes, content, store changes or client work. Readers can subscribe, and the same entry can appear inside your product.
Use the project’s WordPress.org development log, readme or release archive. You do not need ProductLift for that.
Still deciding between a running log and a larger launch story? See changelog vs release notes.
Different kinds of updates
The best format depends on who reads it. Compare minimalist, visual, developer-focused and narrative patterns in these 15 changelog examples.
Keep the marketing site and in-app What’s New experience on the same release history.
Explain new versions, compatibility improvements and fixed issues without editing a static page.
Publish store, policy and checkout updates in a history customers can revisit.
Announce new lessons, resources, events and community improvements.
Give each client a private or branded history of completed work.
Categorize breaking changes, additions and fixes for technical readers.
Publish one cross-platform history rather than losing notes inside app stores.
Use a private changelog to record process, policy and tooling changes for the team.
Add it to your site
Use the official plugin for a shortcode and optional signed SSO, paste the embed into a page builder, or publish the changelog on a hosted custom domain.
Install ProductLift from WordPress.org, connect your portal and place the shortcode on the page.
[productlift_embed tab="changelog"]Paste the hosted embed into Gutenberg, Elementor, Divi, Beaver Builder or another HTML-capable editor.
No changelog tables in WordPressLink to a dedicated changelog, use your branding and reuse it outside WordPress too.
Public or privateUsing a page builder? Follow the specific setup for Elementor, or for Divi and Avada.
Hosted or native
Both can render release notes on a WordPress page. The difference is whether the changelog should remain a WordPress content type or become one release channel used across your site, product and email.
Publish once, place it where it matters
The changelog is the public record. Each connected surface answers a different follow-up question without forcing you to rewrite the release.
Common questions
Install the official ProductLift plugin, connect your portal and place [productlift_embed tab="changelog"] in a Shortcode block. An embed or hosted portal works too.
Yes. Readers can subscribe and receive an email when you publish an update.
Yes. Link the shipped request to the changelog entry so the people following it can see the outcome.
Yes. The What’s New widget and SDK reuse the same changelog entries and can show an unread update dot.
Yes. Translate entries with AI into 28 languages, review them and publish localized versions.
Yes. Import from Headway or CSV. Git2Log can also turn selected commit history or a raw changelog.txt file into a draft for review.
No. ProductLift hosts the entries. WordPress displays the changelog through the official plugin or embed.
The hosted changelog loads asynchronously, so WordPress does not run release-note database queries or render the application itself.
Yes. Use the shortcode where supported, or paste the embed into an HTML or code element.
Choose ProductLift for one changelog across WordPress, your app, email and a hosted portal. Choose native when WordPress-only storage and rendering are the priority.
Ready to make releases visible
Publish the first update, add ProductLift to WordPress and give every release a permanent home.