[Consent banner](/consent-banner)

# Add a cookie consent banner to Svelte

c15t puts the banner in your Svelte app as code. It holds tags until the visitor chooses and keeps Google Consent Mode v2 in sync.

[Start for free](/dashboard/sign-up) · [See the code](#install)

Ask your coding agent: `Add inth to my app: inth.com/SKILL.md`

- **Framework**: Svelte 5.20 and later, without SvelteKit
- **Library**: c15t, open source
- **Code checked**: 28 October 2026

## Install c15t in a Svelte app

c15t is the open source consent library behind Inth Consent. It renders the banner from your own bundle and records each choice in your Inth project.

```bash
npm install c15t @c15t/integrations
```

The `c15t` package gives you the Svelte components from `c15t/svelte` and the Vite plugin from `c15t/svelte/vite`.

Add your Inth project URL to `.env`. Copy it from your Inth dashboard. Vite reads it at build time, so set it before you build.

```bash
VITE_C15T_BACKEND_URL=https://your-project.inth.app
```

Add `consentManifest` to the plugins in `vite.config.ts`. It gives the backend URL to `hosted()` and writes no file into your project.

```ts
import { svelte } from '@sveltejs/vite-plugin-svelte';
import { consentManifest } from 'c15t/svelte/vite';
import { defineConfig } from 'vite';

export default defineConfig({ plugins: [consentManifest(), svelte()] });
```

Code on this page comes from the [c15t Svelte quickstart](https://c15t.com/docs/frameworks/svelte/quickstart), checked 28 October 2026.

Do you use SvelteKit? See the [SvelteKit cookie consent banner](/consent-banner/sveltekit). It puts the banner in the server HTML.

## Mount the provider in App.svelte

Render `ConsentProvider` around your app, with the vendor scripts that c15t loads. The provider starts consent when it mounts, so keep it at the root of the app.

```svelte
<script lang="ts">
  import { posthog } from '@c15t/integrations/posthog';
  import {
    ConsentBanner,
    ConsentDialog,
    ConsentDialogLink,
    ConsentProvider,
    hosted,
  } from 'c15t/svelte';

  const scripts = [
    posthog({
      id: 'phc_your_project_key',
      initOptions: { cookieless_mode: 'never' },
      loadMode: 'after-consent',
    }),
  ];
</script>

<ConsentProvider mode={hosted()} {scripts}>
  <main>
    <h1>c15t + Svelte</h1>
    <p>Your app goes here.</p>
  </main>
  <footer>
    <ConsentDialogLink>Privacy settings</ConsentDialogLink>
  </footer>
  <ConsentBanner />
  <ConsentDialog />
</ConsentProvider>
```

`ConsentDialog` loads in its own chunk after the page. `ConsentDialogLink` lets visitors open their preferences again, so put it in the footer. There is no stylesheet to import.

## Hold scripts until consent

With `loadMode: 'after-consent'`, PostHog waits for measurement permission. Remove any `<script>` tags or SDK imports that already load PostHog, so c15t is the only thing that loads it.

[Svelte scripts and embeds](https://c15t.com/docs/frameworks/svelte/scripts) covers more vendors, iframes and the network blocker. The [c15t integrations](https://c15t.com/docs/integrations/overview) list the helper for each vendor.

## Google Consent Mode v2 in Svelte

The Google tag helper sends the Consent Mode v2 default before your config and an update after each choice. It ships in `@c15t/integrations`.

```ts
import { gtag } from '@c15t/integrations/google-tag';

export const scripts = [gtag({ id: 'G-XXXXXXXXXX', category: 'measurement' })];
```

Add the helper to the `scripts` array in `src/App.svelte`, next to PostHog.

Measurement maps to `analytics_storage`. Marketing maps to `ad_storage`, `ad_user_data` and `ad_personalization`.

By default the helper loads gtag.js before a choice. Google then gets a default that matches the current permissions. Set `loadMode: 'after-consent'` to send nothing to Google until the visitor accepts.

[Read the developer guide to Consent Mode v2](/blog/developer-guide-to-consent-mode-v2).

## Show the right banner in each region

Your Inth project sets a policy for each region, such as opt in for the EU and UK or opt out for California. With `hosted()`, the browser asks your backend for the policy, and the backend reads the visitor’s location from that request. Regional policies need no extra code.

Test each region before launch. [See how regional policies work](/consent-banner/regions).

## When the banner appears

The browser resolves consent after the page loads, so the banner appears after the first paint. `consentManifest()` adds a small script to `index.html` that sends `/init` while your JavaScript downloads.

For a banner in the server HTML, use [SvelteKit](/consent-banner/sveltekit). Measure your own pages before and after you add the banner.

## Check that consent gates work

Build with `vite build`, run `vite preview` and open a private window with the Network tab open. Test under an opt in policy, such as the EU policy.

1. Under an opt in policy, no PostHog request leaves the page before a choice.
2. After Reject All and a reload, PostHog stays off.
3. When you turn on measurement in Privacy settings, PostHog loads.
4. When you turn measurement off, the page reloads without PostHog.

Choices post to your Inth project. Check that Inth has a record for each one. The [c15t verify consent guide](https://c15t.com/docs/guides/verify-consent) has the full release checklist.

## Use Inth in production

c15t is open source. Point it at your Inth project, which hosts the backend and keeps the consent records. [See Inth open source](/oss).

c15t also has a local mode with no backend. It keeps no consent records, so the docs advise against it in production.

Want to see what else your repo sends before consent? [Run a free codebase scan](/run-free-codebase-scan).

## Cookie consent banners for other frameworks

The same banner and the same Inth project work in other stacks. See the setup for [Next.js](/consent-banner/nextjs), [React](/consent-banner/react), [TanStack Start](/consent-banner/tanstack-start), [Nuxt](/consent-banner/nuxt), [Vue](/consent-banner/vue), [Astro](/consent-banner/astro), [SvelteKit](/consent-banner/sveltekit), [HTML](/consent-banner/html) and [JavaScript](/consent-banner/javascript).

[See how the Inth consent banner works](/consent-banner).

## Questions about Svelte consent

### Which package do I install for Svelte?

Install `c15t` and `@c15t/integrations`. The Svelte components come from `c15t/svelte`.

### Which Svelte version does it support?

Svelte 5.20 and later, in a Vite app without SvelteKit.

### Does it work with SvelteKit?

Yes, with server helpers from the same package. See the [SvelteKit cookie consent banner](/consent-banner/sveltekit).

### I use Tailwind CSS 3. How do I load the styles?

Import `c15t/svelte/styles.css` yourself and pass `styles={false}` to the provider.

### How do I set Consent Mode v2 defaults before gtag loads?

Use the c15t Google tag helper. It sends the default before your config and an update after each choice.

### Does it show a different banner in each region?

Yes. Set a policy for each region in your Inth project. c15t applies the policy that matches the visitor’s location. [See regional policies](/consent-banner/regions).

### Can I run it without a backend?

c15t has a local mode with no backend, but it keeps no consent records. Use your Inth project in production.