Cookie banner
Layouts, categories and consent
Your banner, in your colours.
You set the colours, wording and layout of your Kukie.io consent banner and see every change in a live preview, so it looks like part of your site before any visitor sees it.
Watch the walkthrough
Watch one site's banner take on its colours, font, corners and layout in Banner Editor, with every change in the live preview first.
2 minutes 37 seconds, narrated, with captions in the player. The sites and rules in it are examples.
Why it matters
For the first few seconds of a visit, the consent banner is the only thing on the page a visitor can use.
If it arrives in another typeface, another blue and another corner radius, you ask a stranger for permission while looking like a stranger yourself.
Appearance is not what makes a consent banner lawful. What it changes is whether the first thing a visitor meets on your site looks as if you put it there on purpose.
In Banner Editor
You set the look in Banner Editor and check it in a live preview before anything reaches your visitors.
Every colour field takes a HEX or RGB value or a CSS variable from your own stylesheet, so a later change to your brand colour reaches the banner too.
Custom Colours uses what you set. Inherit from Website takes the primary colour from your site, from its theme colour or common brand variables.
The visitor's system fonts, or the font your site already loads, so the banner reads in your typeface.
One radius for the banner and the preferences modal, one for the buttons, so a square card can carry round buttons.
Background, text and border colours for each button, each with a hover state, plus border width and text weight.
Which button sits left, middle and right, and a popup, top bar, bottom bar or floating card in the corner you pick.
| You can change | What that covers | Available on |
|---|---|---|
| Colours and fonts | Primary, background, text and button text colours, Custom Colours or Inherit from Website, and system fonts or your site's font | Every plan |
| Buttons and corners | Colours with hover states, border width and text weight for each button, and separate radii for the banner and the buttons | Every plan |
| Dark appearance | Follows the visitor's device setting with Custom Colours and Auto Dark Mode, both on by default, with an automatic or a custom dark palette | Every plan |
| Layout and order | Popup, top bar, bottom bar or a floating card in one of four positions, the button order, and whether Reject All, Customise, a close button and the policy links appear | Every plan |
| Wording | Heading, body text and button labels in each language you add, plus built-in text in 70+ languages when you turn on Auto-Translation | Every plan |
| Preferences modal and reopen button | The modal's width, button layout, overlay, texts and colours, and the corner, style, icon and colours of the button that brings the banner back | Every plan |
| Your logo | Shown next to the banner title, with its size and corner radius | The Pro, Agency and Unlimited plans |
| Custom CSS | Styling beyond the built-in options, applied inside the banner only | The Pro, Agency and Unlimited plans |
The 4 layouts are as much a consent decision as a visual one: a popup asks for an answer, a bar lets the page carry on. The cookie banner page sets out which to pick and why.
What stays the same
Some of what a banner does is a consent decision rather than a styling one, so it stays the same however you style it.
Style isolation is not a setting you can switch off. Your stylesheet does not restyle the banner, the banner's does not restyle your page, and that holds however far you take the customisation.
Whenever the banner shows a right-to-left language such as Arabic or Hebrew, it mirrors itself. It is not a per-site option you can forget to turn on, and your colour choices cannot break it.
Which controls appear, what they do and how a refusal is honoured are consent decisions. They belong to the banner settings and the region rules, not to the colour picker.
The banner is designed against WCAG 2.2 AA, and how it works from the keyboard and with a screen reader does not change with your colours. Contrast is the part your choices can undermine, which is why the workflow below checks it.
One more item follows your plan rather than your stylesheet: the small 'Powered by Kukie.io' line in the banner. There is a page about what that line means for visitors who select it.
The workflow
The live preview is the whole workflow. It draws the banner as you edit, at the size and on the background it will be used at. Your visitors keep seeing the current banner until you save.
Step 1
The colours that make the banner feel native are the ones already at work on your pages: your button colour, your body text colour, your card background. A logo palette is often more saturated than anything on the live site, and a banner built from it stands out rather than settles in.
Step 2
A colour that looks confident in a picker can look grey behind a paragraph of small text. Change one value at a time and read the preview after each change. It is faster than saving, reloading your own site and trying to remember the previous version.
Step 3
This is the one way a colour choice can damage the banner. Pale text on a pale background passes a brand review and fails a contrast one, and a banner that cannot be read cannot be refused. Banner Editor measures each colour pair as you pick it, including any dark mode colours you set, and says under the field which one falls short and what to change. It never changes your colours: they are yours, and so is that part of the responsibility.
Step 4
Until you save, nothing changes for anybody visiting your site. New visitors get the change once your site's banner file is rebuilt, and a returning visitor's browser can keep the previous version for up to 24 hours. Change your mind next month and the loop is the same.
Variants
Most of the work in styling a consent banner is the variants: the dark one, the mirrored one and the translated ones.
Kukie.io derives the dark and mirrored versions from what you have set, and Auto-Translation supplies the translated ones when you turn it on.
With Custom Colours, the colour mode every site starts with, Auto Dark Mode switches the banner to a dark palette when a visitor's device is in dark mode. You can keep the automatic palette, pick its colours yourself or turn it off.
Choose Inherit from Website instead and the banner takes its colours from your site, with no separate dark mode.
For a right-to-left language such as Arabic or Hebrew, the banner mirrors its layout rather than only swapping the words. Text aligns right, the buttons reverse their order and the switches flip to match.
A translated banner laid out left to right reads as machine-made. A mirrored one reads like the rest of the page.
Turn on Auto-Translation and the banner shows its built-in text in 70+ languages, chosen from the page language or the visitor's browser language.
Wording you write yourself is never machine-translated: add it in each language you want, and Kukie.io shows it as you wrote it.
Beyond the first layer
A visitor who chooses Customise, or comes back later to change their mind, sees two more surfaces. Both take your styling too.
When it matters most
Every site gains from a banner that does not look imported. In these cases it stops being cosmetic.
A client who paid for a design notices a foreign-looking box on their homepage within a day, and it is your phone that rings. Matching the banner for each client is a few minutes of colour work.
A white banner on a dark page is the most obvious sign that a consent tool was added afterwards. Setting the background and text colours fixes it in one pass, and the automatic dark palette covers visitors whose own device is set to dark.
A banner translated into Arabic that still runs left to right tells visitors nobody checked. Mirroring happens by itself, so this is one variant you get without asking for it.
Redesigns, plugin updates and framework upgrades all rewrite CSS underneath you. The banner takes no part in your stylesheet, so none of that reaches it: the banner you approved stays the one your visitors see until you change it.
Set your colours, check the live preview and save. Colour settings, dark mode and the preview are on every plan, including Free.
Appearance is one layer. These pages cover what the banner does, who can use it and how fast it loads.
Layouts, categories and consent
Designed against WCAG 2.2 AA
Async, CDN, config built in
Writing the copy, placing the banner and the design choices to avoid.
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.