Blocked before first contact
External scripts, iframes, images, styles, embeds, fetch calls and dynamically inserted resources are controlled.
Consent management in WordPress
Block optional services before consent and migrate from Borlabs Cookie with a guided process.

100% localConfiguration in WordPress
No telemetryNo product analytics
Fail closedUnknown content stays blocked
GPLv2+Open source licence
Consents, services and records remain in your WordPress installation. External resources start only after the matching choice.
External scripts, iframes, images, styles, embeds, fetch calls and dynamically inserted resources are controlled.
Provider, purpose, domains, data categories, recipients, third countries and retention stay in the local service registry.
Visitors can accept all, reject all or select individual services and withdraw later.
Optionally stores pseudonymous, signed consent records linked to the active configuration.
Permissions are removed, configured browser storage is cleared and blocked content is neutralised again.
The browser test finds what a page really loads. Where wpkookies knows the provider, one click writes the complete service entry — with provider, purpose and every mandatory detail. Addresses it does not know stay blocked and are offered in a guided form.
A catalogue entry alone creates no external connection. Nothing is loaded until the visitor has consented.
Straightforward choices, direct access to settings and local placeholders for blocked content.

Migration from Borlabs Cookie
Borlabs Cookie remains active until final confirmation. Every stage explains what happens and what is still missing.
Detect Borlabs Cookie 2.x or 3.x and show transferable services without changing the live website.
Import services in isolation. Scripts, CSS, regular expressions and shortcodes stay inactive in quarantine.
Check domains, providers, purposes, storage definitions and retention before applying anything.
Check first visit, rejection, granular choice and withdrawal before cutover. Unknown requests must be zero.
Only deactivate Borlabs Cookie after backup and confirmation. A saved snapshot provides a controlled way back.

Migration transfers technical configuration. Sensitive legacy records and legal decisions remain outside its scope.
Each release passes static analysis, automated logic, integration, security and real WordPress workflow tests before publication.
Kookies Consent can be searched, installed and updated straight from the WordPress dashboard. No separate account or cloud connection is required.
Download pluginAlready installed as “WPKookies”? Install Kookies Consent from the WordPress directory. Features and protection logic are identical, and the plugin’s migration takes over your settings.
The key points before installation and migration.
No. The plugin has no cloud connection or telemetry. Configuration and optional records remain in WordPress.
Yes, with the guided assistant. Create a backup and complete the automatic website test before cutover.
No. Old cookies, logs and TCF data are not presented as new consent. Visitors decide again after cutover.
No. wpkookies provides technical consent and blocking functions. Service selection, texts, contracts and legal assessment remain the operator’s responsibility.
The files can be removed. Stored configuration is deleted only if this was explicitly enabled in the settings beforehand.
WordPress 6.9 or later and PHP 8.2 or later are required. The plugin is tested up to WordPress 7.0.
Free download
Free from the official WordPress plugin directory. No registration, cloud or telemetry.