Cookie consent in 2,903 bytes.

A Cookiebot alternative that is 39× smaller

Fetched with curl, compressed with gzip -9, on 7 September 2026. The measurement script ships with the source, so you can re-run it and disagree with us in public.

How to add a cookie banner to any site in three lines

Mark the scripts you want gated, and load the banner. There is no account, no API key, and no dashboard to log into.

<!-- 1. gate a script: type="text/plain" stops the browser loading it -->
<script type="text/plain" data-nc="analytics"
        src="https://www.googletagmanager.com/gtag/js?id=G-XXXX"></script>

<!-- 2. configure, in plain JavaScript -->
<script>window.nanoconsent = { lang: 'en', categories: ['analytics','marketing'] }</script>

<!-- 3. load it -->
<script src="/nanoconsent.min.js"></script>

Cookie consent pricing without a per-site subscription

The banner itself is never a subscription — there is no server to pay for. What an agency subscribes to is keeping it current: rule-pack updates as regulation moves in forty countries, and monitoring that catches what changes on client sites after launch.

Prices in EUR, excluding VAT. EU businesses with a VAT number pay net under reverse charge, and buyers outside the EU pay no EU VAT at all. Your card converts at its own rate — we add nothing to it.

What four years actually cost

And for an agency with thirty client sites

The banner runs on all thirty; the agency licence includes monitoring on 25 of them, and each further 25 sites is €29 a month — the same price as monitoring on its own. On every other row, monitoring is not a line item because it does not exist — nobody is checking whether those thirty setups are still correct.

The setup you ship is correct. It will not stay correct.

Nobody breaks a consent setup on purpose. A client installs a booking plugin, the plugin loads a tracker, and from that afternoon the cookie declaration is wrong and one script is no longer being blocked. The banner still looks fine. Nothing shows up in any dashboard, because nobody is looking.

The uncomfortable part for an agency is where that lands. You built the site. The client will not remember which plugin they installed in March, and the regulator will not care. Monitoring is not a feature of the banner. It is insurance on work that carries your name.

The agency licence includes monitoring on 25 of your sites, all year — the banner itself has no site limit. Not as a bonus — because a licence that keeps the banner current and a service that tells you when a site drifts are the same job, and we would rather sell it as one thing than sell you the banner and hope you notice the rest.

Questions agencies ask before buying

Is there a site limit on the agency licence?

No. The agency licence covers every site you build and maintain for clients, with no cap. There is no server to meter, so a site limit would exist only to create an upsell. The one number you will see is 25 — that is how many sites the included monitoring covers, because monitoring is a service that runs on our server and does cost something. It is not a limit on the banner, and monitoring beyond 25 is €29 a month for each further 25 sites. Bundling nanoconsent into something you resell — a theme, a plugin, a platform — is a separate OEM licence.

What happens if I stop paying?

The banner keeps working. It never depended on a server, so there is nothing that can switch it off. The site licence is paid once. The agency licence is yearly, and when it lapses you stop receiving rule-pack updates, monitoring and support — every banner you have already shipped keeps running exactly as before.

Can I white label the cookie banner for my clients?

Yes. The agency licence removes our credit line and puts your name in the banner instead. White label is included in the €499 a year, not sold as an add-on.

How is it smaller than Cookiebot?

Because it has no back end. Cookiebot's loader fetches an account-specific file behind it — 113,994 bytes gzipped together. nanoconsent is 2,903 bytes and fetches nothing, because the configuration is compiled into the file at build time instead of downloaded on every page load. Measured 7 September 2026.

Does it support Google Consent Mode v2?

Yes. It sends all six Consent Mode v2 signals with wait_for_update, so Google Ads and Analytics receive the consent state instead of guessing at it. That is a different thing from being a Google-certified CMP, which is required only for publishers selling ad space through AdSense, Ad Manager or AdMob — not for advertisers buying ads for their own site.

Why does a consent tool need monitoring?

Because a correct setup stops being correct without anyone touching it. A client installs a plugin, the plugin adds a tracker, and from that day the cookie declaration is wrong and one script is no longer blocked. Nobody notices, because nobody is looking. Monitoring loads every site in a real browser once a month and tells you what changed.

Is nanoconsent GDPR compliant?

No cookie tool can promise that on its own, because compliance depends on how it is configured and what the site actually runs. What we provide is the mechanism: scripts blocked before they load, accept and reject buttons identical as Article 88a requires, consent logged, and the GPC signal honoured. Anyone promising you compliance in a product page is selling you something else.

Do I pay VAT, and can I pay in another currency?

Prices are in EUR and exclude VAT. An EU business with a valid VAT number pays net under the reverse charge mechanism, and a buyer outside the EU pays no EU VAT at all. There is no second currency: we are a Finnish company, the licence is a single payment, and your card converts at its own rate without anything added by us.

Does it work with WordPress?

Yes, and a plugin is in build. Until it ships, the three lines above work on any WordPress theme the same way they work on a hand-written page — there is nothing WordPress-specific about a script tag.

What nanoconsent is not