WP Activity Log Alternative: A Local Audit Trail Without the Upsell
WP Activity Log is the most complete audit plugin for WordPress, and much of what makes it complete sits behind a paid tier. Here is what you get free on both sides.
On this page
A WP Activity Log alternative is worth considering when you want the core of what an audit log does, who did what and when with filters and an export, without the premium tier that WP Activity Log reserves those features for. WP Activity Log is the deepest audit plugin for WordPress and earns its reputation. For many sites it is also more than they need, with the useful parts paywalled. This post sets out what each side gives you free.
We make DevDome Activity Log, so WP Activity Log and Simple History come first.
WP Activity Log (Melapress)
The reference point for WordPress auditing. It tracks hundreds of distinct event types across users, content, settings, plugins, themes, multisite and a long list of third-party plugins including WooCommerce, Yoast and popular form builders. Each event has a code, a severity and a detailed message.
Where it is better. Depth and coverage. If you need to know that a WooCommerce product’s price changed from one value to another, or which Yoast setting was altered, this is the plugin that records it. The premium tier adds email and SMS alerts, saved reports, search with filters, external log storage and user session control, which together make it suitable for compliance audits.
Where it falls short. The free version is a log viewer. Search and filtering, reports, notifications and off-site storage are premium, and the premium prompts are present in the admin. For a small site that wants “who deleted the page”, the free version shows the answer only if you scroll. Check their listing for the current feature split; it changes.
Simple History
A long-standing free plugin that presents events as a readable timeline: “Editor Anna updated the post Pricing”, with a dashboard widget and an RSS feed option. It tracks core events and a reasonable set of plugins.
Where it is better. It is genuinely simple and well maintained. The feed format is easy for non-technical owners to read, and the quick search at the top covers most needs.
Where it falls short. It is a feed, not a table. Filtering by user and event type exists but is lighter, there is no CSV export in core, and the tracked event set is smaller. Fine for one site run by its owner; less suited to handing a filtered export to a client or an insurer.
DevDome Activity Log
Our plugin records account, content and settings events locally: logins and failed logins with IP, user creation and role changes, posts and pages across their lifecycle, media, plugin and theme changes, and nine groups of site settings. The admin screen is a table with filters by user, event type and date, a search box, and CSV export. Retention defaults to 90 days and is adjustable, with privacy controls for what is stored. Every feature is free and no account is needed. On WordPress 6.9 and newer it also registers abilities so AI tools can query the log.
Where it is better. The filtered table, search and export are free, with no premium tier to upgrade to and no prompts asking you to.
Where it falls short. Coverage is narrower than WP Activity Log. It does not track third-party plugin internals like product price changes or SEO settings, and it has no email alerts or external storage. If you need those, it is the wrong tool.
What to check before you choose
Three questions settle most decisions faster than a feature list.
Who reads the log? If it is you, on one site, a feed is fine and a table is a bonus. If it is a client, an insurer or a developer you hand an export to, you want filters and CSV, and that rules out the free tier of WP Activity Log and the core of Simple History.
What must it record? Write down the five events you would actually search for. For most owners it is logins, user changes, plugin changes, published and deleted content, and settings. All three cover those. If the list includes WooCommerce order edits, SEO settings or form entries, only WP Activity Log tracks them in depth.
Where must it live? Local storage with a retention window is fine for almost everyone. If a compliance requirement says the log must survive an administrator wiping it, you need external storage, which is a premium feature in WP Activity Log and absent in the other two; scheduled CSV exports to somewhere off-site are the cheap approximation.
Retention and privacy on all three
Every one of these plugins stores personal data about your contributors: usernames, IP addresses, timestamps of what they did. The sensible settings are the same whichever you pick. Keep retention short, around 90 days, because real investigations rarely reach further back and a two-year log is a larger exposure for no benefit. Log the action, never the content of passwords or private fields. Restrict the log screen to administrators. And tell your team the log exists and why, which for EU and UK contributors is the kind of thing a privacy notice should mention. That is not legal advice; it is the shape of what the regulators publish, and all three plugins can be configured to follow it.
Side by side
| WP Activity Log (free) | Simple History | DevDome Activity Log | |
|---|---|---|---|
| Event depth | Very high | Medium | Account, content, settings |
| Third-party plugin events | Many | Some | No |
| Filters and search | Premium | Basic | Free |
| CSV export | Premium | No | Free |
| Email alerts | Premium | No | No |
| External storage | Premium | No | No |
| Retention control | Yes | Yes | Yes, 90-day default |
| Upsell prompts | Yes | Minimal | None |
Which to pick
Compliance, WooCommerce detail or alerting: WP Activity Log, and budget for the premium tier, because that is where those features live.
One site, you just want to read what happened: Simple History. The feed is pleasant and free.
Filtered table, search and export without a licence, across several sites: DevDome Activity Log. Install it, set retention, and it sits quietly until the day you need it.
In every case, install before the incident. A log that starts after the question was asked cannot answer it.
Related reading: How to See Who Logged Into Your WordPress Site.
Key takeaways
- WP Activity Log records hundreds of event types in detail and integrates with many plugins. In depth, nothing else matches it.
- Its free version limits reports, search, email alerts and external storage; those are the premium features.
- DevDome Activity Log covers account, content and settings events with filters, search and CSV export, all free, with no account and no premium tier.
- Simple History is the other lightweight option: free, well maintained, with a feed-style view rather than a filtered table.
- Pick WP Activity Log for compliance-grade depth and alerting. Pick a lightweight log if you want who-changed-what without a licence.
Sources
- WP Activity Log on WordPress.org : free versus premium split and tracked event list
- Melapress: WP Activity Log documentation : features, integrations and storage options
- Simple History on WordPress.org : the lightweight feed-style alternative
Links last checked October 17, 2026.
Frequently asked questions
What does the free version of WP Activity Log leave out?
The premium tier adds reports, search with filters, email and SMS notifications, external database and log storage, session management and some integrations. The free version records events and shows the log. Check their listing for the current split.
Is Simple History a good alternative?
Yes, for many sites. It is free, maintained and shows events as a readable feed with a dashboard widget. It is less of a filtered table than a timeline, and it has a smaller set of tracked events. If you prefer a feed over a table, try it.
Do I need external log storage?
Only if you must prove the log was not tampered with by someone who had admin access, which is a compliance requirement for some businesses. Most small sites are fine with a local log and regular CSV exports.
Will any of these slow my site?
Not for visitors. All three write a row when an admin action happens and nothing on normal page loads. Retention settings keep the table small.