A CookieConsent v3 alternative with hosted records
CookieConsent v3 is a vanilla JavaScript plugin that keeps consent in the browser. Inth Consent runs the open source c15t banner as code in your app and hosts the records.
Why switch from CookieConsent v3
No records to show
On CookieConsent v3
CookieConsent v3 does not store consent records, and has no built-in logging API.
With Inth Consent
Inth Consent hosts every saved choice with its region and policy version, and each region gets its own rules.
One rule for every region
On CookieConsent v3
The plugin shows the same banner rules everywhere.
With Inth Consent
Each region gets its own rule: opt-in, opt-out or no banner. See regional banners.
A switch nobody has time to plan
On CookieConsent v3
Moving off CookieConsent v3 means finding every tag, category and script it controls.
With Inth Consent
Paste the prompt under How to move from CookieConsent v3 into your coding agent. It maps your setup to c15t and plans a staging run.
How Inth Consent and CookieConsent v3 compare
For privacy and legal teams: Inth records every choice with its region and policy version, applies each region’s own rules and honors Global Privacy Control.
| Your requirements | Inth Consent | CookieConsent v3 |
|---|---|---|
| Inth ahead | ||
| Consent state in your code and server renderThe first render already knows the visitor’s choice, so nothing flashes or starts early. | Next.js and TanStack Start resolve consent on the server, per request | Vanilla JavaScript plugin that runs in the browser |
| The banner as your own componentCopy and design changes ship in a pull request, in your design system. | Ready components in your framework, with themes, component parts or headless hooks | Configurable plugin UI, styled with CSS |
| Agent migration briefYour coding agent can plan the move from your own codebase. | Copy the prompt under How to move from CookieConsent v3 into your coding agent | No brief for this move |
| Hosted consent recordsYou can show what each visitor chose, and when. | Every saved choice, region and policy version in your Inth dashboard | Does not store consent records; you send them with your own code |
| Regional rules and Global Privacy ControlEach visitor sees the banner their region requires. | Opt-in, opt-out or no banner by country and US state; reads the Global Privacy Control signal. See regional banners | Honors Global Privacy Control with respectGpc; no regional rules |
| IAB TCFAd tech partners read consent through the IAB framework. | IAB TCF 2.4 through @c15t/iab. Inth is a registered IAB Europe CMP, ID 490 | Does not implement IAB TCF |
| Both | ||
| Open source, no lock-inYou can read, fork and keep the code that decides when each script runs. | c15t is open source under Apache-2.0. See Inth open source | Open source under the MIT license |
| Pricing you can work outYou can budget for growth before you talk to sales. | c15t is free under Apache-2.0. Inth plans add hosted records, starting with a Free plan | Free under the MIT license |
| Google Consent Mode v2Google Ads and Analytics need denied defaults and an update after each choice. | The Google Tag Manager helper sends the denied default before gtm.js, then an update after each choice | Google Consent Mode guide |
| Script, iframe and network blockingNothing optional runs before the visitor says yes. | Script loader, iframe blocker and network blocker tied to consent categories | Blocks scripts you tag with a category |
CookieConsent v3 details come from its public docs and pricing pages, read on October 30, 2026. Read the developer comparison.
What each costs as traffic grows
| Traffic | Inth Consent | CookieConsent v3 |
|---|---|---|
| 10,000 visits a month | $86 a month on Starter | Free (MIT license) |
| 100,000 visits a month | $474 a month on Pro | Free (MIT license) |
| 1,000,000 visits a month, or talk to us about Enterprise | $4,374 a month on Business | Free (MIT license) |
CookieConsent introduction, . Bots and AI agents don't count as sessions, and reloads within 30 minutes count once, so you may pay for fewer sessions than your visits. CookieConsent v3 is free and keeps consent in the browser, with no hosted records. Inth plans add hosted records and regional rules.
Banner speed
CookieConsent v3 is not in the current CookieBench run
Inth Consent
25 ms median banner visibility; +104 KB initial transfer vs no CMP (Next.js desktop lab)
CookieConsent v3
CookieBench has not measured CookieConsent v3 in its current run, so this page makes no speed claim against it. Inth, the team behind c15t, maintains CookieBench, and c15t is one of the tools it measures. Lab results; your site may differ.
CookieBench results. CookieBench cookiebench-v3.2.4, published 14 November 2026. Inth, the team behind c15t, maintains CookieBench, and c15t is one of the tools measured. Lab results; your site may differ.
How to move from CookieConsent v3
Bring your current setup and what you need to record. We’ll map the switch with you.
Contact salesPaste this into your coding agent
Plan a migration from CookieConsent v3 to Inth Consent, built on c15t, for this codebase. Find the CookieConsent v3 setup and Consent Mode wiring, map every tag to a c15t integration and consent category, propose how to run c15t on a staging route while CookieConsent v3 stays live, and list what to verify before cutting over. Use https://c15t.com/docs/comparisons/cookieconsent-v3 and https://c15t.com/docs/integrations/overview.
Questions about the switch
Yes. The c15t Google Tag Manager helper sends the Consent Mode v2 denied default before gtm.js loads, then an update after each choice. Map your categories, then check each tag after a visitor choice.
CookieConsent v3 keeps each choice in the visitor’s browser, so there are no hosted records to move. If your own code logs choices, we plan together what to keep, and Inth records every choice from the switch on. Ask counsel how long to keep the old records.
Yes. Use c15t themes, replace component parts or build your own markup with the headless hooks. The banner then uses your design system.
Yes. Each region gets its own rule: opt-in, opt-out or no banner. c15t reads the Global Privacy Control signal and never stores it as a refusal the visitor did not make. See regional banners.
Inth Consent runs on c15t, which is open source under the Apache-2.0 license. See Inth open source.
Yes. Inth has a SOC 2 Type 2 report, shared under NDA. Request it from the Trust center or read about the audit.
Paste the prompt under How to move from CookieConsent v3 into your coding agent to map your CookieConsent v3 categories and tags. Then run both banners against the same visitor journeys on a staging route. Talk to us about your setup.