Conzent vs WP Legal Pages

WPLP Cookie Consent is GPL-2.0 and keeps consent logs in your own WordPress database — the ownership argument is one it already makes. The differences are TCF version, what happens outside WordPress, and whether the published tier limits agree with each other.

✓ Apache 2.0 self-hosted core ✓ IAB TCF v2.4 ✓ 6 native CMS integrations

Start with the part that deserves credit: the WPLP Cookie Consent repository is licensed GPL-2.0, and the WordPress.org listing says consent logging is stored in the site's own database. That is a real ownership position, not a marketing one, and it is more than most CMPs in this category offer. The free tier is unusually complete for compliance software — banner, built-in cookie scanner, automatic script and content blocking, category consent, preference centre, consent logging, Google Consent Mode v2 and WP Consent API support, with the listing explicitly stating no visitor, traffic or pageview caps. Paid pricing is published and low: Lite at $0, Professional at $8/month billed yearly and Business at $12/month billed yearly, with the published platform profile also showing $48/yr and $72/yr equivalents and site-count tiers at 25 sites for $28/mo or $170/yr, 50 sites for $53/mo or $330/yr and 100 sites for $100/mo or $640/yr. Note that the unit price falls as sites are added — the same shape Conzent uses. We are not going to pretend that is a differentiator.

Where it gets harder is that the published limits do not agree with each other. The WordPress.org listing says no visitor-based limits and no pageview limits; a WP Legal Pages comparison post describes the free version as up to 3 sites with 100 pages per scan and Pro as up to 10 sites with 20,000 pages per scan; a third-party review describes paid plans as 50 scans a month, 10,000 pages per scan and 100,000 pageviews a month. Those cannot all be current at once, and it matters for anyone sizing a plan for a client portfolio. IAB TCF is the second open question: a third-party review reports TCF 2.2, but the vendor's own product documentation surfaced publicly does not confirm a version for the current release. If you need TCF, get that in writing. The third difference is structural: it is a WordPress plugin, so a Drupal, TYPO3 or Umbraco property in the same portfolio needs a separate tool and keeps a separate consent record.

Conzent WPLP Cookie Consent
Pricing model Per site, not per view — the per-site price drops as you add sites, and traffic never changes it. See current tiers Also per site: Lite $0, Professional $8/mo billed yearly, Business $12/mo billed yearly; published profile adds 25 sites $28/mo or $170/yr, 50 sites $53/mo or $330/yr, 100 sites $100/mo or $640/yr
What happens when you grow The unit price falls — no allowance to exceed, no overage rate, and no cap on self-hosted Site-count tiers up to 100. Published limits conflict — the plugin listing says no pageview caps, a vendor post says 3 sites free / 10 sites Pro, a review reports 100,000 pageviews/month on paid
GDPR / IAB TCF / Consent Mode v2 ✓ GDPR, CCPA & 25+ regional laws
✓ IAB TCF v2.4
✓ Consent Mode v2 (Basic & Advanced) — all included, every plan
Google Consent Mode v2 and WP Consent API confirmed on the plugin listing, free tier included. TCF version unconfirmed by vendor documentation — a third-party review reports TCF 2.2
CMS & platform integrations 6 native integrations: WordPress, Wix, Joomla, Drupal, TYPO3, Umbraco — plus a universal script tag for anything else WordPress only — the consent layer is part of the WordPress install
Self-hosted / open source ✓ Yes — OCI image, Apache 2.0, one-line installer, unlimited sites and pageviews ✓ Yes — repository licensed GPL-2.0, and the plugin runs entirely on your own server
EU data residency ✓ Yes — managed cloud data hosted in Germany; self-host it and it never leaves your own server Consent logs sit in your site's own database, so residency follows your hosting. The public docs do not state which tables are used or what the retention policy is
Free tier ✓ Free forever if self-hosted; free trial on managed cloud ✓ Genuinely capable — scanner, blocking, consent logging, Consent Mode v2 and WP Consent API are all listed as free

WPLP figures are taken from its public pricing page, its WordPress.org plugin listing, its published platform profile, its GitHub repository and third-party reviews, all current in 2026. Where those sources disagree we have said so rather than picking one. Confirm the numbers with WP Legal Pages before you switch. See Conzent's current plans.

Because WPLP keeps consent records in your own database, you are in a better position than most people migrating a CMP: the data is on infrastructure you control, so export it on your own schedule rather than the vendor's. Take that export before you deactivate the plugin, not after. The rest is the usual sequence — run the new script alongside the plugin for a test window, re-scan to rebuild your cookie categories, configure and preview the banner, then cut over and deactivate. Two checks worth making. If other plugins on the site read the WP Consent API signal, confirm what they do when the writer of that signal changes. And test the consent state against GTM in preview mode on a cold cache before you sign it off — that applies to any CMP swap, not just this one.

Limits you can plan against

Conzent's self-hosted build has no site or pageview ceiling under Apache 2.0, and the managed tiers are published per site. You should not need three sources and a support ticket to work out how many sites your plan covers.

TCF v2.4, stated on the record

If you are running programmatic inventory, the TCF version is not a detail. Conzent runs IAB TCF v2.4 and Consent Mode v2 in both Basic and Advanced on every plan, self-hosted included. WPLP's own documentation does not currently state a TCF version for the shipping release.

One consent layer for a mixed estate

A plugin's consent record lives inside one WordPress install. Conzent runs as its own service with native integrations for WordPress, Wix, Joomla, Drupal, TYPO3 and Umbraco plus a universal script tag — one configuration and one log across the portfolio.

Frequently asked questions

How much does WPLP Cookie Consent cost?

Its public pricing page lists Lite at $0, Professional at $8/month billed yearly and Business at $12/month billed yearly. The published platform profile adds larger tiers: 25 sites at $28/mo or $170/yr, 50 sites at $53/mo or $330/yr and 100 sites at $100/mo or $640/yr. Confirm current pricing directly.

Is WP Legal Pages open source?

Yes — the WPLP Cookie Consent repository is licensed GPL-2.0. Conzent's core is Apache 2.0. Both are open-source licences; they differ in what they require of derivative work, which is a question for whoever handles your licensing, not a quality ranking.

Does WPLP support IAB TCF?

A third-party review reports IAB TCF 2.2, but the vendor's own public product documentation does not confirm a version for the current release. If TCF matters to your ad stack, ask WP Legal Pages to state the version in writing. Conzent runs TCF v2.4 on every plan.

Where does WPLP store consent logs?

The WordPress.org listing says consent logging is stored in the site's own database, so it sits on your hosting. The public documentation does not state which tables are used or what the retention behaviour is — worth checking before you rely on it for an audit trail.

Open source, and not only on WordPress.

Apache 2.0 core you can self-host for free, TCF v2.4 and Consent Mode v2 on every plan, six CMS integrations plus a universal script tag.