Skip to main content

c15t vs Silktide Consent Manager

Compare c15t with Silktide Consent Manager. See regional rules, consent records, IAB TCF, Google Consent Mode and framework support in each.

Get started

c15t vs Silktide Consent Manager 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, IAB GPP and Global Privacy Control. Silktide Consent Manager documents none of these.

Silktide Consent Manager is a free browser script from Silktide, with an MIT licence. You add one JavaScript file and one CSS file, then define consent types. It adds scripts after consent and sends Google Consent Mode updates. It keeps each visitor's choices only in that visitor's browser.

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

What you needc15tSilktide Consent Manager
Apply different rules by regionPolicy rules by country and US state. Inth or your backend finds the locationOne default for each consent type, for all visitors. No location detection
Keep consent records on a serverInth hosts the backend and keeps records in its database. Self-hosting is optionalNot included. Choices stay in browser storage
Use IAB TCFTCF 2.4 with the @c15t/iab add-on. Inth is a registered IAB Europe CMP, ID 490Not documented
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 updateConsent Mode updates for each consent type, and a dataLayer event
Use consent in framework componentsNative adapters and reactive consent stateBrowser global with callbacks
Resolve consent in Next.jsServer, streamed and browser pathsBrowser setup only
Translate the interfaceBuilt-in copy in 53 languages, with your own i18n messagesConfigurable text
Show preferencesCategory and vendor controlsConfigurable consent types and a preferences modal
Control scriptsIntegration helpers, network request rules and embedsScript injection for each consent type, and callbacks
Handle withdrawalReload by default. Optional cleanup of declared dataReload after the visitor withdraws consent for injected scripts
Change the interfaceThemes, component parts and headless APIsConfigurable text, position and CSS variables
Licence and priceApache 2.0, with no licence fee. Inth has a free plan and paid plansMIT and free, with no traffic or domain limits
Installc15t from npm, or @c15t/browser as a script tagOne JavaScript file and one CSS file, self-hosted or from a CDN

Sources: Silktide product scope and configuration and source.

What you build yourself with Silktide Consent Manager.

Silktide Consent Manager gives you a banner, preferences and script injection 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. Code that connects choices to your application state, because it has no framework adapters.

c15t and Inth include all three. Silktide documents no IAB TCF support. If ad partners need a TC string from your site, Silktide 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.

Silktide Consent Manager does not find the visitor's location. Each consent type has one defaultValue, and the same default 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 Silktide Consent Manager 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