Skip to main content

c15t vs CookieConsent v3

Compare c15t with CookieConsent v3, the vanilla-cookieconsent package. See regional rules, consent records, IAB TCF, Google Consent Mode and framework support.

Get started

c15t vs CookieConsent v3 feature comparison.

c15t is the better choice for most production sites. It applies consent rules by region, so visitors outside opt-in regions do not wait behind a banner. Inth keeps your consent records. c15t also supports IAB TCF 2.4, Global Privacy Control and Google Consent Mode v2. With CookieConsent v3, you build most of these parts yourself. IAB TCF is not available.

CookieConsent v3 is a free browser library by Orest Bida, with an MIT licence. Its npm package is vanilla-cookieconsent. Its own documentation says that it is not a CMP, does not store consent records and does not support IAB TCF.

Start on Inth's free plan and follow the framework guide for your app.

What you needc15tCookieConsent v3
Apply different rules by regionPolicy rules by country and US state. Inth or your backend finds the locationOne mode for all visitors, opt-in by default. For a mode per country, you find the location yourself
Keep consent records on a serverInth hosts the backend and keeps records in its database. Self-hosting is optionalNot included. Callbacks can send records to an endpoint that you build
Use IAB TCFTCF 2.4 with the @c15t/iab add-on. Inth is a registered IAB Europe CMP, ID 490Not supported
Respect privacy signalsReads Global Privacy Control. IAB GPP API for US state opt-outsNot documented
Use Google Consent Mode v2Google tag and GTM integrations send the default and each updateExample code that you connect to its consent callbacks
Use consent in framework componentsNative adapters and reactive consent stateBrowser library, with framework setup recipes
Resolve consent in Next.jsServer, streamed and browser pathsBrowser setup. Its React example starts in an effect
Translate the interfaceBuilt-in copy in 53 languages, with your own i18n messagesNo default translations. You supply each language
Show preferencesCategory and vendor controlsCategory controls and a switch for each service
Control scriptsRegistered integrations, network request rules and embedsScript attributes and service callbacks
Clear cookies after withdrawalOptional rules for each category. A refusal for one vendor needs separate cleanupCookie cleanup for each category and service
Change the interfaceThemes, component parts and headless APIsModal options, CSS and custom content
Licence and priceApache 2.0, with no licence fee. Inth has a free plan and paid plansMIT, with no licence fee. You pay to host any parts that you build
Installc15t from npm, or @c15t/browser as a script tagvanilla-cookieconsent from npm, or a CDN script

Sources: introduction, setup, configuration, consent records, script controls, Google Consent Mode and the npm package.

What you build yourself with CookieConsent v3.

CookieConsent v3 gives you a banner and switches in the browser. Your team builds and runs the rest:

  1. A location lookup, to apply different rules by region.
  2. A consent record endpoint and its storage, to prove what each visitor chose.
  3. Consent Mode code, to send the Google signals at the correct time.
  4. Language files, because the library has no default translations.

c15t and Inth include all four. CookieConsent does not support IAB TCF. If ad partners need a TC string from your site, CookieConsent cannot supply one.

<include src="../shared/comparisons/inth-hosting.mdx" />

Ask for consent only where your policy needs it.

When your policy lets scripts run before a choice in a region, c15t runs them there. You keep the analytics and ad data from those visitors. Visitors in opt-in regions still see the banner before optional scripts run.

c15t picks a policy rule for each visitor from their location. The recommendedPolicyRules() pack uses opt-in rules for Europe and Québec. It uses opt-out rules for supported US privacy states. Other known locations get no banner. A visitor from an unknown country gets strict opt-in.

Inth or your own backend finds the location. Browser-only mode does not find the visitor's country.

CookieConsent v3 does not find the visitor's location. Its default opt-in mode applies to all visitors. The banner shows to all visitors, also where your policy lets optional scripts run before a choice. Until those visitors accept, you lose their analytics and ad data.

Before you let categories run by default, compare the preset with how you use the data. A country match does not give a legal basis for a vendor's use of data.

Moving off CookieConsent v3 across many sites?

Inth builds c15t and runs migrations for large teams, from the first audit to the day you remove the old script.

Talk to Inth

Install c15t. Get 44 integrations.

c15t maintains each typed helper. Most helpers load their vendor only after consent, and stop it when the visitor withdraws consent.

Import each helper from @c15t/integrations.

Browse the integrations

Start in minutes.

Paste this line into your agent. It reads the setup brief and does each step.

Ask your coding agent

The setup brief is at /SKILL.md. For the docs, agents can read /llms.txt and /llms-full.txt, or use the MCP server at with no sign-in.

Inth hosts the backend, the policy rules and the IAB CMP ID.

Compare c15t with your consent tool.

The facts about each tool come from its own published pages.

Read the comparison overview