Cookiebot Pricing: What You Get on Free vs Premium

As a monthly subscription per website, with the fee determined by how many subpages that site has. Pricing is published on the site, so you can check the tier for your own page count directly. Larger or less obvious cases can request a non-binding offer rather than estimating.

Submit your domain and email through the pricing page and the system counts your subpages, then sends an offer by email, typically within 24 hours. You can run the free version while waiting, so there is no need to pause the implementation until pricing is settled.

One domain and up to 100 subpages within a single domain group, supporting one legislation only, whether that is GDPR, ePrivacy or CCPA. Both plans provide what is needed to make a site's cookie use and tracking compliant. The difference is scale and flexibility rather than a compliance gap in the free tier.

Not comfortably. Single-legislation support means one framework's rules apply to everyone, which is a problem when opt-in and opt-out models both need serving. A site with genuinely mixed traffic needs multiple legislation support, which is where the paid tier becomes necessary rather than merely convenient.

Logo upload and custom color schemes are premium features. The free plan uses the standard color scheme with no logo. Beyond aesthetics this affects performance, since a banner that visibly belongs to the site tends to earn better opt-in rates than a generic one.

Multi-language display with automatic detection of the visitor's language is a premium feature. For any site with an international audience this matters more than it first appears, since a consent request someone cannot read is unlikely to produce informed consent in any meaningful sense.

A feature allowing one consent decision to apply across all your domains and subdomains, enabled in the backend manager. It suits businesses running several related properties, since visitors are not asked repeatedly as they move between them. It is a premium capability rather than a free one.

Yes, through internal domain aliases, which let you run the platform on non-production domains including development, test and staging environments and local servers. This is a premium feature, and it is the practical way to verify blocking works before exposing a configuration to real visitors.