Own your consent code. No vendor script on your page.
Your code, your repo. The Consent banner runs on c15t, our open-source library, so it ships in your bundle. Style it in your product. Debug it in your app.
Your page stays stable. The banner shifts no layout.
The banner is fast and stays stable because c15t ships in your bundle. In the CookieBench Next.js desktop run, total blocking time was 0 ms and layout shift was 0.00.
That run used a local test backend, and the banner made 0 third-party requests there. In production, the banner sends consent choices to your Inth project.
- DesktopBanner visible at 25 ms
- Emulated mobileBanner visible at 252 ms
The clock starts at the page request.
Playback is slow so that you can follow it. The times are the measured medians.
- Desktop main-content paint
- +16 ms
- Emulated mobile main-content paint
- +400 ms
- Desktop initial transfer
- +104 KB
Inth maintains CookieBench and does not rank the tools in it. These figures show the tested setups, not an order.
- Inth, the team behind c15t, maintains CookieBench, and c15t is one of the tools measured.
- Lab results; your site may differ.
Source: CookieBench cookiebench-v3.2.4, published 14 November 2026. See the run limits.
Set it up with one command, then review the code.
One command sets you up. The c15t CLI adds the provider, the banner and the privacy settings. You review the code, change it and ship it in your usual pull request.
To install by hand, follow the quickstart for your framework. The Consent banner page lists the same steps.
npx @c15t/cli setup- Detected Next.js (App Router)
- Added ConsentManagerProvider
- Added the consent banner and privacy settings
- Done. Review the changes.
What you change in code is what visitors see.
Start with theme tokens and props. If you need more, move the parts of the banner or build your own UI on the same consent state.
<ConsentManagerProvider options={{ theme: { colors: { primary: '' } }, colorScheme: '', i18n: { locale: '', messages: { en: { cookieBanner: { title: '' }, }, }, }, }}> <ConsentBanner primaryButton= /></ConsentManagerProvider>Style with your own CSS
Use your own components, tokens and themes. The banner then looks like the rest of your product.
Translations
Keep the banner copy and its regional versions in the same translation system as your app.
Your UI, same state. One hook feeds every surface.
The stock banner and the inline widget are c15t components, the same code you ship. Your UI reads the same consent state through a hook, so a choice in one shows in all.
- Strictly Necessary
necessary - Needed for the site to work.
- Analytics
measurement - How visitors find and use the site.
- Marketing
marketing - Ads and how well they work.
In code, the name of the Analytics category is measurement. Hosted mode keeps the consent choices in your Inth project, at your backendURL.
import { ConsentBanner, ConsentDialog, ConsentManagerProvider,} from '@c15t/react';<ConsentManagerProvider options={{ mode: 'hosted', backendURL: 'https://your-project.inth.app', consentCategories: ['necessary', 'measurement', 'marketing'], }}> <ConsentBanner /> <ConsentDialog /></ConsentManagerProvider>Shared consent state
Visitors revisit consent from any page with ConsentDialogTrigger.
One component, consent anywhere. ConsentDialogTrigger is a small button over the page that opens the privacy settings. Visitors drag it to any corner. You choose when it shows.
Drag the button to another corner, or use the arrow keys.
<ConsentDialogTrigger icon="fingerprint" showWhen="always"/>The visitor’s choice loads videos and maps.
c15t puts a placeholder where each YouTube video or Google map goes. The page sends no request to YouTube or Google until the visitor allows the category for that embed.
With c15t
Debug consent like your own code.
In development, the c15t dev tools add a panel to your page. It shows the visitor’s location, the matched policy, each category’s value and the scripts that loaded.