diff --git a/README.md b/README.md
index a318d3de..ae754a5f 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,6 @@ A lightweight, modular, and performant state management ecosystem for building m
 | [`@nano_kit/platform-web`](packages/platform-web#readme) | Web platform adapters and reactive helpers. | [![NPM version][platform-web-npm]][platform-web-npm-url] |
 | [`@nano_kit/router`](packages/router#readme) | Routing library, built on @nano_kit/store. | [![NPM version][router-npm]][router-npm-url] |
 | [`@nano_kit/query`](packages/query#readme) | Data fetching and caching library, built on @nano_kit/store. | [![NPM version][query-npm]][query-npm-url] |
-| [`@nano_kit/cookie-store`](packages/cookie-store#readme) | CookieStore-compatible implementation for SSR and testing environments. | [![NPM version][cookie-store-npm]][cookie-store-npm-url] |
 | [`@nano_kit/ssr`](packages/ssr#readme) | Base package for server-side rendering capabilities. | [![NPM version][ssr-npm]][ssr-npm-url] |
 | [`@nano_kit/react`](packages/react#readme) | React integration for @nano_kit/store. | [![NPM version][react-npm]][react-npm-url] |
 | [`@nano_kit/react-router`](packages/react-router#readme) | React integration for @nano_kit/router. | [![NPM version][react-router-npm]][react-router-npm-url] |
@@ -24,6 +23,7 @@ A lightweight, modular, and performant state management ecosystem for building m
 | [`@nano_kit/svelte`](packages/svelte#readme) | Svelte integration for @nano_kit/store. | [![NPM version][svelte-npm]][svelte-npm-url] |
 | [`@nano_kit/svelte-router`](packages/svelte-router#readme) | Svelte integration for @nano_kit/router. | [![NPM version][svelte-router-npm]][svelte-router-npm-url] |
 | [`@nano_kit/svelte-ssr`](packages/svelte-ssr#readme) | Svelte adapter for server-side rendering capabilities. | [![NPM version][svelte-ssr-npm]][svelte-ssr-npm-url] |
+| [`@nano_kit/svelte-kit`](packages/svelte-kit#readme) | SvelteKit integration for stores, router, and SSR. | [![NPM version][svelte-kit-npm]][svelte-kit-npm-url] |
 | [`@nano_kit/next-router`](packages/next-router#readme) | Next.js integration for @nano_kit/router. | [![NPM version][next-router-npm]][next-router-npm-url] |
 
 <!-- nanoviews -->
@@ -61,11 +61,6 @@ A lightweight, modular, and performant state management ecosystem for building m
 [query-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fquery.svg
 [query-npm-url]: https://npmjs.com/package/@nano_kit/query
 
-<!-- cookie-store -->
-
-[cookie-store-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fcookie-store.svg
-[cookie-store-npm-url]: https://npmjs.com/package/@nano_kit/cookie-store
-
 <!-- ssr -->
 
 [ssr-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fssr.svg
@@ -116,6 +111,11 @@ A lightweight, modular, and performant state management ecosystem for building m
 [svelte-ssr-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fsvelte-ssr.svg
 [svelte-ssr-npm-url]: https://npmjs.com/package/@nano_kit/svelte-ssr
 
+<!-- svelte-kit -->
+
+[svelte-kit-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fsvelte-kit.svg
+[svelte-kit-npm-url]: https://npmjs.com/package/@nano_kit/svelte-kit
+
 <!-- next-router -->
 
 [next-router-npm]: https://img.shields.io/npm/v/%40nano_kit%2Fnext-router.svg
diff --git a/website/src/content/docs/examples/rick-and-morty.mdx b/website/src/content/docs/examples/rick-and-morty.mdx
index 35a5c7cd..4211ce48 100644
--- a/website/src/content/docs/examples/rick-and-morty.mdx
+++ b/website/src/content/docs/examples/rick-and-morty.mdx
@@ -9,7 +9,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'
 
 This example shows a larger encyclopedia app built around routing, data loading, and server-side rendering.
 
-Compare the tabs to see the same application model running with React SSR, Next.js App Router, and Next.js Pages Router.
+Compare the tabs to see the same application model running with React SSR, Svelte SSR, SvelteKit, Next.js App Router, and Next.js Pages Router.
 
 <Tabs syncKey='example-view'>
   <TabItem label='React SSR' icon='seti:react'>
@@ -36,6 +36,18 @@ Compare the tabs to see the same application model running with React SSR, Next.
 
     [View source on GitHub](https://github.com/TrigenSoftware/nano_kit/tree/main/examples/rick-and-morty/svelte-nano_kit-ssr)
   </TabItem>
+  <TabItem label='SvelteKit' icon='seti:svelte'>
+    <iframe
+      src='https://stackblitz.com/github/TrigenSoftware/nano_kit/tree/main/examples/rick-and-morty/svelte-kit-nano_kit-ssr?embed=1&file=src%2Froutes%2F%2Blayout.svelte&view=both'
+      loading='lazy'
+      style='width: 100%; height: 500px; border: 0; border-radius: 4px; overflow: hidden;'
+      title='Rick and Morty Encyclopedia built with SvelteKit and Nano Kit'
+      allow='accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking'
+      sandbox='allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts'
+    />
+
+    [View source on GitHub](https://github.com/TrigenSoftware/nano_kit/tree/main/examples/rick-and-morty/svelte-kit-nano_kit-ssr)
+  </TabItem>
   <TabItem label='Next.js App Router' icon='vercel'>
     <iframe
       src='https://codesandbox.io/p/sandbox/github/TrigenSoftware/nano_kit/tree/main/examples/rick-and-morty/next-app-nano_kit-ssr?embed=1&file=%2Fsrc%2Fapp%2Flayout.tsx'
diff --git a/website/src/content/docs/examples/session.mdx b/website/src/content/docs/examples/session.mdx
index b1e16186..599b5769 100644
--- a/website/src/content/docs/examples/session.mdx
+++ b/website/src/content/docs/examples/session.mdx
@@ -5,21 +5,37 @@ sidebar:
   order: 6
 ---
 
-import { Aside } from '@astrojs/starlight/components'
+import { Aside, Tabs, TabItem } from '@astrojs/starlight/components'
 
-This example shows a small React SSR app that keeps a username in a `session` cookie.
+This example shows a small SSR app that keeps a username in a `session` cookie.
 
 It demonstrates request-bound cookie state, `cookieStored`, SSR rendering from incoming cookies, server-side cookie deletion on `/logout`, redirect handling, and hydration without mismatches.
 
 <Aside>StackBlitz runs this example in a sandbox with a fake cookie implementation, so session behavior can be slightly inaccurate there.</Aside>
 
-<iframe
-  src='https://stackblitz.com/github/TrigenSoftware/nano_kit/tree/main/examples/session/react-nano_kit-ssr?embed=1&file=src%2Findex.tsx&view=both'
-  loading='lazy'
-  style='width: 100%; height: 500px; border: 0; border-radius: 4px; overflow: hidden;'
-  title='Session Cookies built with React SSR and Nano Kit'
-  allow='accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking'
-  sandbox='allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts'
-/>
+<Tabs syncKey='example-view'>
+  <TabItem label='React SSR' icon='seti:react'>
+    <iframe
+      src='https://stackblitz.com/github/TrigenSoftware/nano_kit/tree/main/examples/session/react-nano_kit-ssr?embed=1&file=src%2Findex.tsx&view=both'
+      loading='lazy'
+      style='width: 100%; height: 500px; border: 0; border-radius: 4px; overflow: hidden;'
+      title='Session Cookies built with React SSR and Nano Kit'
+      allow='accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking'
+      sandbox='allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts'
+    />
 
-[View source on GitHub](https://github.com/TrigenSoftware/nano_kit/tree/main/examples/session/react-nano_kit-ssr)
+    [View source on GitHub](https://github.com/TrigenSoftware/nano_kit/tree/main/examples/session/react-nano_kit-ssr)
+  </TabItem>
+  <TabItem label='SvelteKit' icon='seti:svelte'>
+    <iframe
+      src='https://stackblitz.com/github/TrigenSoftware/nano_kit/tree/main/examples/session/svelte-kit-nano_kit-ssr?embed=1&file=src%2Froutes%2F%2Blayout.svelte&view=both'
+      loading='lazy'
+      style='width: 100%; height: 500px; border: 0; border-radius: 4px; overflow: hidden;'
+      title='Session Cookies built with SvelteKit and Nano Kit'
+      allow='accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking'
+      sandbox='allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts'
+    />
+
+    [View source on GitHub](https://github.com/TrigenSoftware/nano_kit/tree/main/examples/session/svelte-kit-nano_kit-ssr)
+  </TabItem>
+</Tabs>
diff --git a/website/src/content/docs/getting-started/index.mdx b/website/src/content/docs/getting-started/index.mdx
index c588bb31..82f27db9 100644
--- a/website/src/content/docs/getting-started/index.mdx
+++ b/website/src/content/docs/getting-started/index.mdx
@@ -65,6 +65,7 @@ unsub()
 | [@nano_kit/svelte](/integrations/svelte) | Svelte integration for @nano_kit/store. |
 | [@nano_kit/svelte-router](/integrations/svelte-router) | Svelte integration for @nano_kit/router. |
 | [@nano_kit/svelte-ssr](/integrations/svelte-ssr) | Svelte SSR adapter for @nano_kit/ssr. |
+| [@nano_kit/svelte-kit](/integrations/svelte-kit) | SvelteKit integration for stores, router, and SSR. |
 | [@nano_kit/next-router](/integrations/next-router) | Next.js integration for @nano_kit/router. |
 
 ## Motivation
diff --git a/website/src/content/docs/integrations/index.mdx b/website/src/content/docs/integrations/index.mdx
index eb3d24e2..c26f10e5 100644
--- a/website/src/content/docs/integrations/index.mdx
+++ b/website/src/content/docs/integrations/index.mdx
@@ -18,4 +18,5 @@ Nano Kit keeps its core framework-agnostic, then adds thin adapters for renderin
 | [@nano_kit/svelte](/integrations/svelte) | Svelte integration for @nano_kit/store. |
 | [@nano_kit/svelte-router](/integrations/svelte-router) | Svelte integration for @nano_kit/router. |
 | [@nano_kit/svelte-ssr](/integrations/svelte-ssr) | Svelte SSR adapter for @nano_kit/ssr. |
+| [@nano_kit/svelte-kit](/integrations/svelte-kit) | SvelteKit integration for stores, router, and SSR. |
 | [@nano_kit/next-router](/integrations/next-router) | Next.js integration for @nano_kit/router. |
diff --git a/website/src/content/docs/integrations/next-router.mdx b/website/src/content/docs/integrations/next-router.mdx
index 6942c014..de12853d 100644
--- a/website/src/content/docs/integrations/next-router.mdx
+++ b/website/src/content/docs/integrations/next-router.mdx
@@ -2,7 +2,7 @@
 title: Next.js Router
 description: "Integrate @nano_kit/router with Next.js using @nano_kit/next-router."
 sidebar:
-  order: 12
+  order: 13
 ---
 
 import { Tabs, TabItem, Code } from '@astrojs/starlight/components'
@@ -132,19 +132,23 @@ export default function App({ Component, pageProps }: AppProps) {
 }
 ```
 
-For SSR data loading in `getServerSideProps`, use `virtualNavigationContext` together with `dehydrate`.
+For SSR data loading in `getServerSideProps`, create a virtual navigation for the current URL and pass its providers to `dehydrate`.
 
 ```tsx
 import type { GetServerSideProps } from 'next'
-import { dehydrate } from '@nano_kit/store'
-import { virtualNavigationContext } from '@nano_kit/next-router'
+import { dehydrate, provide } from '@nano_kit/store'
+import { Location$, Navigation$, virtualNavigation } from '@nano_kit/next-router'
 import { routes } from '@/stores/router'
 import CharactersPage, { Stores$ } from '@/ui/pages/Characters'
 
 export const getServerSideProps: GetServerSideProps = async (context) => {
+  const [$location, navigation] = virtualNavigation(context.resolvedUrl, routes)
   const dehydrated = await dehydrate(
     Stores$,
-    virtualNavigationContext(context.resolvedUrl, routes)
+    [
+      provide(Location$, $location),
+      provide(Navigation$, navigation)
+    ]
   )
 
   return {
@@ -228,21 +232,25 @@ These helpers are for the Pages Router.
 
 ```tsx
 import type { GetServerSideProps } from 'next'
-import { contextDehydrate } from '@nano_kit/store'
+import { InjectionContext, dehydrate, provide } from '@nano_kit/store'
 import {
+  Location$,
+  Navigation$,
   notFound,
   redirect,
-  virtualNavigationContext
+  virtualNavigation
 } from '@nano_kit/next-router'
 import { routes } from '@/stores/router'
 import { User$ } from '@/stores/user'
 import UserPage, { Stores$ } from '@/ui/pages/User'
 
 export const getServerSideProps: GetServerSideProps = async (nextContext) => {
-  const [context, dehydrated] = await contextDehydrate(
-    Stores$,
-    virtualNavigationContext(nextContext.resolvedUrl, routes)
-  )
+  const [$location, navigation] = virtualNavigation(nextContext.resolvedUrl, routes)
+  const context = new InjectionContext([
+    provide(Location$, $location),
+    provide(Navigation$, navigation)
+  ])
+  const dehydrated = await dehydrate(Stores$, context)
   const { $user } = context.get(User$)
 
   return notFound($user()) ?? redirect(context) ?? {
diff --git a/website/src/content/docs/integrations/next.mdx b/website/src/content/docs/integrations/next.mdx
index 1b4935a3..ea514b71 100644
--- a/website/src/content/docs/integrations/next.mdx
+++ b/website/src/content/docs/integrations/next.mdx
@@ -2,7 +2,7 @@
 title: Next.js
 description: "Use Nano Kit with Next.js via @nano_kit/react and @nano_kit/next-router."
 sidebar:
-  order: 11
+  order: 12
 ---
 
 import { Tabs, TabItem, Code } from '@astrojs/starlight/components'
@@ -168,7 +168,7 @@ If you do not use `@nano_kit/router`, render `StaticDehydration` directly withou
 In the Pages Router, the usual setup is:
 
 - [`HydrationProvider`](/integrations/react#hydrationprovider) in `_app.tsx`
-- [`dehydrate()`](/store/ssr#server-side-dehydration) or [`contextDehydrate()`](/store/ssr#server-side-dehydration) in `getServerSideProps`
+- [`dehydrate()`](/store/ssr#server-side-dehydration) in `getServerSideProps`
 - [`NextNavigationProvider`](/integrations/next-router#nextnavigationprovider) when the app uses `@nano_kit/router`
 
 ### `_app.tsx`
@@ -203,19 +203,23 @@ export default function App({ Component, pageProps }: AppProps) {
 
 When you need server-prefetched store data, dehydrate stores in `getServerSideProps` and pass the snapshot through `pageProps.dehydrated`.
 
-If the page uses `@nano_kit/router`, create the dehydration context with [`virtualNavigationContext`](/integrations/next-router#pages-router).
+If the page uses `@nano_kit/router`, create a virtual navigation for the current URL and pass its providers as the second `dehydrate` argument.
 
 ```tsx
 import type { GetServerSideProps } from 'next'
-import { dehydrate } from '@nano_kit/store'
-import { virtualNavigationContext } from '@nano_kit/next-router'
+import { dehydrate, provide } from '@nano_kit/store'
+import { Location$, Navigation$, virtualNavigation } from '@nano_kit/next-router'
 import { routes } from '@/stores/router'
 import CharactersPage, { Stores$ } from '@/ui/pages/Characters'
 
 export const getServerSideProps: GetServerSideProps = async (context) => {
+  const [$location, navigation] = virtualNavigation(context.resolvedUrl, routes)
   const dehydrated = await dehydrate(
     Stores$,
-    virtualNavigationContext(context.resolvedUrl, routes)
+    [
+      provide(Location$, $location),
+      provide(Navigation$, navigation)
+    ]
   )
 
   return {
@@ -234,17 +238,26 @@ If you want the Pages Router to behave like static dehydration in the App Router
 
 ```tsx
 import type { GetServerSideProps } from 'next'
-import { dehydrate } from '@nano_kit/store'
+import { dehydrate, provide } from '@nano_kit/store'
 import { isFlight } from '@nano_kit/react'
-import { virtualNavigationContext } from '@nano_kit/next-router'
+import { Location$, Navigation$, virtualNavigation } from '@nano_kit/next-router'
 import { routes } from '@/stores/router'
 import CharactersPage, { Stores$ } from '@/ui/pages/Characters'
 
 export const getServerSideProps: GetServerSideProps = async (context) => {
-  const dehydrated = !isFlight(context.req.headers) && await dehydrate(
-    Stores$,
-    virtualNavigationContext(context.resolvedUrl, routes)
-  )
+  let dehydrated
+
+  if (!isFlight(context.req.headers)) {
+    const [$location, navigation] = virtualNavigation(context.resolvedUrl, routes)
+
+    dehydrated = await dehydrate(
+      Stores$,
+      [
+        provide(Location$, $location),
+        provide(Navigation$, navigation)
+      ]
+    )
+  }
 
   return {
     props: {
@@ -258,7 +271,7 @@ export default function Page() {
 }
 ```
 
-Without `@nano_kit/router`, call `dehydrate(Stores$)` without `virtualNavigationContext`.
+Without `@nano_kit/router`, call `dehydrate(Stores$)` without navigation providers.
 
 ## Which Package Does What?
 
diff --git a/website/src/content/docs/integrations/preact-ssr.mdx b/website/src/content/docs/integrations/preact-ssr.mdx
index efa5ea09..2d11482f 100644
--- a/website/src/content/docs/integrations/preact-ssr.mdx
+++ b/website/src/content/docs/integrations/preact-ssr.mdx
@@ -76,8 +76,6 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
    - **`vite dev`** — starts the development server with SSR rendering handled in-process.
    - **`vite build`** — produces `dist/client/` (browser assets) and `dist/renderer/` (SSR renderer bundle).
 
-   Add `cookieStore: true` when SSR stores need access to request cookies. See [SSR Cookies](/ssr/cookies) for the full setup.
-
 3. **Write your production HTTP server**
 
    For production, write your own HTTP server that imports the built renderer and calls `renderer.render(url)` for every incoming request:
@@ -88,7 +86,10 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
    // Express example
    app.get('*', async (req, res) => {
-     const result = await renderer.render(req.url, req.headers.cookie)
+     const result = await renderer.render(req.url, {
+       cookie: req.headers.cookie,
+       acceptLanguage: req.headers['accept-language']
+     })
 
      if (result.setCookieHeaders) {
        res.setHeader('Set-Cookie', result.setCookieHeaders)
@@ -108,6 +109,32 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
 </Steps>
 
+## SSR Options
+
+The SSR plugin can provide request-bound browser-like dependencies for stores that run during server rendering.
+
+### `cookieStore`
+
+Use `cookieStore: true` when the renderer should provide a request-bound `CookieStore$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. See [SSR Cookies](/ssr/cookies) for the full setup, including store code and `Set-Cookie` forwarding.
+
+```js
+ssr({
+  index: 'src/index.tsx',
+  cookieStore: true
+})
+```
+
+### `browserLocale`
+
+Use `browserLocale: true` when the renderer should provide request-bound `Locales$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. The renderer parses the incoming `Accept-Language` header with [`parseLocales`](/platform/web/#locale), so universal stores can inject `Locales$` and resolve the same locale shape on the server and in the browser. See [SSR Locale](/ssr/locale) for the full setup.
+
+```js
+ssr({
+  index: 'src/index.tsx',
+  browserLocale: true
+})
+```
+
 ## Custom Renderer
 
 To customize the HTML output, extend `PreactRenderer` and override `renderToString`:
@@ -178,6 +205,7 @@ ssr({
 ## See Also
 
 - [SSR — Getting Started](/ssr) — how the base SSR package works
-- [SSR Cookies](/ssr/cookies) — request-bound cookies, `cookieStore: true`, and `Set-Cookie` forwarding
+- [SSR Cookies](/ssr/cookies) — request-bound cookies and `Set-Cookie` forwarding
+- [SSR Locale](/ssr/locale) — request-bound locales and `Accept-Language` parsing
 - [Router SSR](/router/ssr) — how to add [`Stores$`](/router/ssr#stores-data-dehydration) and [`Head$`](/router/ssr#head-management) to page modules
 - [Preact Router](/integrations/preact-router) — [`App`](/integrations/preact-router#app), [`browserNavigation`](/integrations/preact-router#setup), [`router`](/integrations/preact-router#router), and other Preact router APIs
diff --git a/website/src/content/docs/integrations/react-ssr.mdx b/website/src/content/docs/integrations/react-ssr.mdx
index bc7efcfc..482d5de6 100644
--- a/website/src/content/docs/integrations/react-ssr.mdx
+++ b/website/src/content/docs/integrations/react-ssr.mdx
@@ -76,8 +76,6 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
    - **`vite dev`** — starts the development server with SSR rendering handled in-process.
    - **`vite build`** — produces `dist/client/` (browser assets) and `dist/renderer/` (SSR renderer bundle).
 
-   Add `cookieStore: true` when SSR stores need access to request cookies. See [SSR Cookies](/ssr/cookies) for the full setup.
-
 3. **Write your production HTTP server**
 
    For production, write your own HTTP server that imports the built renderer and calls `renderer.render(url)` for every incoming request:
@@ -88,7 +86,10 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
    // Express example
    app.get('*', async (req, res) => {
-     const result = await renderer.render(req.url, req.headers.cookie)
+     const result = await renderer.render(req.url, {
+       cookie: req.headers.cookie,
+       acceptLanguage: req.headers['accept-language']
+     })
 
      if (result.setCookieHeaders) {
        res.setHeader('Set-Cookie', result.setCookieHeaders)
@@ -108,6 +109,32 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
 </Steps>
 
+## SSR Options
+
+The SSR plugin can provide request-bound browser-like dependencies for stores that run during server rendering.
+
+### `cookieStore`
+
+Use `cookieStore: true` when the renderer should provide a request-bound `CookieStore$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. See [SSR Cookies](/ssr/cookies) for the full setup, including store code and `Set-Cookie` forwarding.
+
+```js
+ssr({
+  index: 'src/index.ts',
+  cookieStore: true
+})
+```
+
+### `browserLocale`
+
+Use `browserLocale: true` when the renderer should provide request-bound `Locales$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. The renderer parses the incoming `Accept-Language` header with [`parseLocales`](/platform/web/#locale), so universal stores can inject `Locales$` and resolve the same locale shape on the server and in the browser. See [SSR Locale](/ssr/locale) for the full setup.
+
+```js
+ssr({
+  index: 'src/index.ts',
+  browserLocale: true
+})
+```
+
 ## Custom Renderer
 
 To customize the HTML output, extend `ReactRenderer` and override `renderToString`:
@@ -178,6 +205,7 @@ ssr({
 ## See Also
 
 - [SSR — Getting Started](/ssr) — how the base SSR package works
-- [SSR Cookies](/ssr/cookies) — request-bound cookies, `cookieStore: true`, and `Set-Cookie` forwarding
+- [SSR Cookies](/ssr/cookies) — request-bound cookies and `Set-Cookie` forwarding
+- [SSR Locale](/ssr/locale) — request-bound locales and `Accept-Language` parsing
 - [Router SSR](/router/ssr) — how to add [`Stores$`](/router/ssr#stores-data-dehydration) and [`Head$`](/router/ssr#head-management) to page modules
 - [React Router](/integrations/react-router) — [`App`](/integrations/react-router#app), [`browserNavigation`](/integrations/react-router#setup), [`router`](/integrations/react-router#router), and other React router APIs
diff --git a/website/src/content/docs/integrations/react.mdx b/website/src/content/docs/integrations/react.mdx
index add6c4f5..37e1d9b8 100644
--- a/website/src/content/docs/integrations/react.mdx
+++ b/website/src/content/docs/integrations/react.mdx
@@ -176,11 +176,15 @@ export default function Page() {
 }
 ```
 
-If you need to inspect or act on the dehydrated data or injection context before rendering, use [`serverDehydrate`](#serverdehydrate--servercontextdehydrate) or [`serverContextDehydrate`](#serverdehydrate--servercontextdehydrate) directly and pass the snapshot via `dehydrated`:
+If you need to run dehydration manually before rendering, use [`dehydrate`](#dehydrate) directly and pass the snapshot via `dehydrated`:
 
 ```tsx
 import { inject } from '@nano_kit/store'
-import { serverContextDehydrate, Dehydration } from '@nano_kit/react'
+import {
+  Dehydration,
+  dehydrate,
+  getDehydrationContext
+} from '@nano_kit/react'
 import { User$ } from './stores'
 
 function Stores$() {
@@ -191,7 +195,8 @@ function Stores$() {
 }
 
 export default async function Page() {
-  const [context, dehydrated] = await serverContextDehydrate(Stores$)
+  const dehydrated = await dehydrate(Stores$)
+  const context = getDehydrationContext()
 
   /* ...You can use `context` or `dehydrated` here to implement some logic before rendering... */
 
@@ -206,6 +211,7 @@ export default async function Page() {
 Props:
 - `stores?` — function returning an array of accessors to dehydrate
 - `dehydrated?` — pre-dehydrated data (skips `stores` dehydration if provided)
+- `context?` — additional providers to inject into the server context before dehydration
 - `isolate?` — create a new `InjectionContext` on the client instead of reusing the existing one
 
 #### `StaticDehydration`
@@ -238,6 +244,7 @@ export default function Page() {
 Props:
 - `stores?` — function returning an array of accessors to dehydrate
 - `dehydrated?` — pre-dehydrated data (skips `stores` dehydration if provided)
+- `context?` — additional providers to inject into the server context before dehydration
 - `isolate?` — create a new `InjectionContext` on the client instead of reusing the existing one
 - `flight?` — override flight detection; when `false`, dehydration is always included
 
@@ -261,16 +268,20 @@ export default function RootLayout({ children }) {
 }
 ```
 
-#### `serverDehydrate` / `serverContextDehydrate`
+#### `dehydrate`
 
-Low-level RSC helpers that run stores in the **shared per-request injection context** and return the dehydrated snapshot. Use them when you need to inspect or act on the dehydrated data before rendering — for instance, to redirect if the user is not authenticated.
+Low-level RSC helper that runs stores in the **shared per-request injection context** and returns the dehydrated snapshot. Use it when you need to manually prepare a snapshot before rendering instead of letting `Dehydration` or `StaticDehydration` run stores from their `stores` prop.
 
-`serverDehydrate` returns only the snapshot; `serverContextDehydrate` also returns the `InjectionContext` so you can read values from it.
+After `dehydrate(Stores$)` resolves, the stores have already run and populated their data. Use `getDehydrationContext()` when you need request-time logic based on those populated stores, such as redirecting when a loaded user is missing.
 
 ```tsx
 import { redirect } from 'next/navigation'
 import { inject } from '@nano_kit/store'
-import { serverContextDehydrate, Dehydration } from '@nano_kit/react'
+import {
+  Dehydration,
+  dehydrate,
+  getDehydrationContext
+} from '@nano_kit/react'
 import { User$ } from './stores'
 
 function Stores$() {
@@ -280,7 +291,8 @@ function Stores$() {
 }
 
 export default async function Page() {
-  const [context, dehydrated] = await serverContextDehydrate(Stores$)
+  const dehydrated = await dehydrate(Stores$)
+  const context = getDehydrationContext()
   const { $user } = context.get(User$)
 
   if (!$user()) {
@@ -316,7 +328,7 @@ function App({ dehydrated }) {
 Props:
 - `dehydrated?` — dehydrated key-value pairs `[string, unknown][]`, or a falsy value to skip hydration
 - `context?` — additional injection providers
-- `reuse?` — reuse an existing `InjectionContext` instead of creating a new one; set to `true` if you want the hydration context to be shared with the rest of your app instead of isolated
+- `reuse?` — reuse an existing `InjectionContext` instead of creating a new one; `true` by default
 
 #### `StaticHydrationProvider`
 
diff --git a/website/src/content/docs/integrations/svelte-kit.mdx b/website/src/content/docs/integrations/svelte-kit.mdx
new file mode 100644
index 00000000..9a28e10f
--- /dev/null
+++ b/website/src/content/docs/integrations/svelte-kit.mdx
@@ -0,0 +1,262 @@
+---
+title: SvelteKit
+description: "Use Nano Kit stores, routing helpers, and SSR hydration in SvelteKit."
+sidebar:
+  order: 11
+---
+
+import { Steps, Tabs, TabItem, Code } from '@astrojs/starlight/components'
+
+The `@nano_kit/svelte-kit` package integrates Nano Kit with SvelteKit. It re-exports everything from `@nano_kit/svelte` and `@nano_kit/svelte-router`, and adds SvelteKit-specific helpers for store dehydration, client hydration, navigation, router-aware links, and server cookies.
+
+## Installation
+
+Install the package using your favorite package manager:
+
+<Tabs syncKey='pkg'>
+  <TabItem label='pnpm' icon='pnpm'>
+    <Code frame='none' lang='bash' code='pnpm add @nano_kit/store @nano_kit/router @nano_kit/svelte-kit' />
+  </TabItem>
+  <TabItem label='Yarn' icon='seti:yarn'>
+    <Code frame='none' lang='bash' code='yarn add @nano_kit/store @nano_kit/router @nano_kit/svelte-kit' />
+  </TabItem>
+  <TabItem label='npm' icon='seti:npm'>
+    <Code frame='none' lang='bash' code='npm install @nano_kit/store @nano_kit/router @nano_kit/svelte-kit' />
+  </TabItem>
+</Tabs>
+
+## Quick Start
+
+The main SvelteKit integration point is store dehydration in `+page.server.ts` and hydration in the matching `+page.svelte`.
+
+<Steps>
+
+1. **Set up the root layout**
+
+   Create a request-scoped dehydration context in the root server layout and pass its reference to the root layout component.
+
+   ```ts
+   // src/routes/+layout.server.ts
+   import {
+     setDehydrationContext
+   } from '@nano_kit/svelte-kit'
+   import type { LayoutServerLoad } from './$types'
+
+   export const load: LayoutServerLoad = () => {
+     const contextRef = setDehydrationContext()
+
+     return {
+       contextRef
+     }
+   }
+   ```
+
+   ```svelte
+   <!-- src/routes/+layout.svelte -->
+   <script lang="ts">
+     import { setHydrationContext } from '@nano_kit/svelte-kit'
+
+     let { data, children } = $props()
+
+     setHydrationContext({
+       fromRef: () => data.contextRef
+     })
+   </script>
+
+   {@render children()}
+   ```
+
+2. **Dehydrate page stores**
+
+   Choose whether SvelteKit should dehydrate stores during client-side navigations.
+
+   <Tabs syncKey='svelte-kit-dehydration'>
+     <TabItem label='No flight dehydration'>
+
+       ```ts
+       // src/routes/characters/+page.server.ts
+       import {
+         dehydrate,
+         isFlight
+       } from '@nano_kit/svelte-kit'
+       import { Stores$ } from '$lib/pages/Characters.svelte'
+       import type { PageServerLoad } from './$types'
+
+       export const load: PageServerLoad = async () => ({
+         dehydrated: !isFlight() && await dehydrate(Stores$)
+       })
+       ```
+
+       `isFlight()` skips server dehydration during browser navigation. Stores still work, but navigation-time data is fetched in the browser instead of being prepared by the SvelteKit server load.
+
+     </TabItem>
+     <TabItem label='Flight dehydration'>
+
+       ```ts
+       // src/routes/characters/+page.server.ts
+       import { dehydrate } from '@nano_kit/svelte-kit'
+       import { Stores$ } from '$lib/pages/Characters.svelte'
+       import type { PageServerLoad } from './$types'
+
+       export const load: PageServerLoad = async ({ parent }) => {
+         await parent()
+
+         return {
+           dehydrated: await dehydrate(Stores$)
+         }
+       }
+       ```
+
+       Use this mode when you want server data preparation during browser navigation too. `await parent()` is needed when those stores rely on providers installed by a parent layout, such as router navigation or cookies.
+
+     </TabItem>
+   </Tabs>
+
+3. **Hydrate page stores**
+
+   Pass the dehydrated page data to `setHydrationContext` in the page component.
+
+   ```svelte
+   <!-- src/routes/characters/+page.svelte -->
+   <script lang="ts">
+     import { setHydrationContext } from '@nano_kit/svelte-kit'
+     import CharactersPage from '$lib/pages/Characters.svelte'
+
+     let { data } = $props()
+
+     setHydrationContext({
+       dehydrated: () => data.dehydrated
+     })
+   </script>
+
+   <CharactersPage />
+   ```
+
+</Steps>
+
+## Navigation
+
+Set up navigation only when stores or components use Nano Kit router dependencies such as `Location$`, `Navigation$`, `Link`, or typed route navigation.
+
+### Server Navigation
+
+In the root server layout, provide request navigation.
+
+```ts
+// src/routes/+layout.server.ts
+import { provide } from '@nano_kit/store'
+import {
+  Location$,
+  Navigation$,
+  serverNavigation,
+  setDehydrationContext
+} from '@nano_kit/svelte-kit'
+import { routes } from '$lib/stores/router'
+import type { LayoutServerLoad } from './$types'
+
+export const load: LayoutServerLoad = () => {
+  const [location, navigation] = serverNavigation(routes)
+  const contextRef = setDehydrationContext([
+    provide(Location$, location),
+    provide(Navigation$, navigation)
+  ])
+
+  return {
+    contextRef
+  }
+}
+```
+
+### Client Navigation
+
+In the root layout component, provide browser navigation.
+
+```svelte
+<!-- src/routes/+layout.svelte -->
+<script lang="ts">
+  import { provide } from '@nano_kit/store'
+  import {
+    Link,
+    Location$,
+    Navigation$,
+    getKitNavigation,
+    setHydrationContext
+  } from '@nano_kit/svelte-kit'
+  import { routes } from '$lib/stores/router'
+
+  let { data, children } = $props()
+  const [location, navigation] = getKitNavigation(routes)
+
+  setHydrationContext({
+    fromRef: () => data.contextRef,
+    context: [
+      provide(Location$, location),
+      provide(Navigation$, navigation)
+    ]
+  })
+</script>
+
+<nav>
+  <Link to="home">Home</Link>
+  <Link to="characters">Characters</Link>
+</nav>
+
+{@render children()}
+```
+
+## Cookies
+
+`@nano_kit/svelte-kit` exports `CookieStore`, a server adapter around SvelteKit's `cookies` object. Provide it through [`CookieStore$`](/platform/web/#cookies) when stores use cookie-backed signals.
+
+```ts
+// src/routes/+layout.server.ts
+import { provide } from '@nano_kit/store'
+import {
+  CookieStore,
+  setDehydrationContext
+} from '@nano_kit/svelte-kit'
+import { CookieStore$ } from '@nano_kit/platform-web'
+import type { LayoutServerLoad } from './$types'
+
+export const load: LayoutServerLoad = ({ cookies }) => {
+  const contextRef = setDehydrationContext([
+    provide(CookieStore$, new CookieStore(cookies))
+  ])
+
+  return {
+    contextRef
+  }
+}
+```
+
+Then inject `CookieStore$` in stores that use cookie-backed signals.
+
+```ts
+// src/lib/stores/session.ts
+import { inject } from '@nano_kit/store'
+import {
+  CookieStore$,
+  cookieStored
+} from '@nano_kit/platform-web'
+
+export function Session$() {
+  const cookieStore = inject(CookieStore$)
+  const $session = cookieStored<string | null>(cookieStore, {
+    name: 'session',
+    path: '/',
+    sameSite: 'lax'
+  }, null)
+
+  return {
+    $session
+  }
+}
+```
+
+See [SSR Cookies](/ssr/cookies) for the general cookie model.
+
+## See Also
+
+- [Svelte](/integrations/svelte) - Svelte bindings for Nano Kit stores and dependency injection
+- [Svelte Router](/integrations/svelte-router) - typed links and router-aware Svelte components
+- [SSR Cookies](/ssr/cookies) - request-bound cookies and `Set-Cookie` forwarding
diff --git a/website/src/content/docs/integrations/svelte-ssr.mdx b/website/src/content/docs/integrations/svelte-ssr.mdx
index 0f6e5d4b..74215d64 100644
--- a/website/src/content/docs/integrations/svelte-ssr.mdx
+++ b/website/src/content/docs/integrations/svelte-ssr.mdx
@@ -76,8 +76,6 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
    - **`vite dev`** — starts the development server with SSR rendering handled in-process.
    - **`vite build`** — produces `dist/client/` (browser assets) and `dist/renderer/` (SSR renderer bundle).
 
-   Add `cookieStore: true` when SSR stores need access to request cookies. See [SSR Cookies](/ssr/cookies) for the full setup.
-
 3. **Write your production HTTP server**
 
    For production, write your own HTTP server that imports the built renderer and calls `renderer.render(url)` for every incoming request:
@@ -88,7 +86,10 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
    // Express example
    app.get('*', async (req, res) => {
-     const result = await renderer.render(req.url, req.headers.cookie)
+     const result = await renderer.render(req.url, {
+       cookie: req.headers.cookie,
+       acceptLanguage: req.headers['accept-language']
+     })
 
      if (result.setCookieHeaders) {
        res.setHeader('Set-Cookie', result.setCookieHeaders)
@@ -108,6 +109,32 @@ import { Steps, Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components
 
 </Steps>
 
+## SSR Options
+
+The SSR plugin can provide request-bound browser-like dependencies for stores that run during server rendering.
+
+### `cookieStore`
+
+Use `cookieStore: true` when the renderer should provide a request-bound `CookieStore$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. See [SSR Cookies](/ssr/cookies) for the full setup, including store code and `Set-Cookie` forwarding.
+
+```js
+ssr({
+  index: 'src/index.ts',
+  cookieStore: true
+})
+```
+
+### `browserLocale`
+
+Use `browserLocale: true` when the renderer should provide request-bound `Locales$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. The renderer parses the incoming `Accept-Language` header with [`parseLocales`](/platform/web/#locale), so universal stores can inject `Locales$` and resolve the same locale shape on the server and in the browser. See [SSR Locale](/ssr/locale) for the full setup.
+
+```js
+ssr({
+  index: 'src/index.ts',
+  browserLocale: true
+})
+```
+
 ## Custom Renderer
 
 To customize the HTML output, extend `SvelteRenderer` and override `renderToString`:
@@ -179,6 +206,7 @@ ssr({
 ## See Also
 
 - [SSR — Getting Started](/ssr) — how the base SSR package works
-- [SSR Cookies](/ssr/cookies) — request-bound cookies, `cookieStore: true`, and `Set-Cookie` forwarding
+- [SSR Cookies](/ssr/cookies) — request-bound cookies and `Set-Cookie` forwarding
+- [SSR Locale](/ssr/locale) — request-bound locales and `Accept-Language` parsing
 - [Router SSR](/router/ssr) — how to add [`Stores$`](/router/ssr#stores-data-dehydration) and [`Head$`](/router/ssr#head-management) to page modules
 - [Svelte Router](/integrations/svelte-router) — [`App`](/integrations/svelte-router#app), [`browserNavigation`](/integrations/svelte-router#setup), [`router`](/integrations/svelte-router#router), and other Svelte router APIs
diff --git a/website/src/content/docs/platform/web.mdx b/website/src/content/docs/platform/web.mdx
index 9d170a2d..80164d82 100644
--- a/website/src/content/docs/platform/web.mdx
+++ b/website/src/content/docs/platform/web.mdx
@@ -213,6 +213,59 @@ Use `cookieStored` when you only need reads and writes. Use `syncedCookieStored`
 
 Assigning `null` or `undefined` deletes the underlying cookie through the provided [`CookieStore`](https://developer.mozilla.org/en-US/docs/Web/API/Cookie_Store_API)-compatible object. When `cookieStored` was created from options, deletion reuses the matching `path`, `domain`, and `partitioned` attributes so the browser removes the same cookie scope. If a default value was provided, the signal falls back to it after deletion.
 
+For universal code, use the `CookieStore$` injection token. By default it returns the browser `cookieStore`, so browser-only code does not need any setup.
+
+```ts
+import { inject } from '@nano_kit/store'
+import {
+  CookieStore$,
+  cookieStored
+} from '@nano_kit/platform-web'
+
+export function Session$() {
+  const cookieStore = inject(CookieStore$)
+  const $session = cookieStored<string | null>(cookieStore, {
+    name: 'session',
+    path: '/',
+    sameSite: 'lax'
+  }, null)
+
+  return {
+    $session
+  }
+}
+```
+
+During SSR and tests, provide `CookieStore$` with `VirtualCookieStore`. It implements the CookieStore API from an incoming `Cookie` header and collects pending `Set-Cookie` headers from mutations.
+
+```ts
+import { InjectionContext, provide } from '@nano_kit/store'
+import {
+  CookieStore$,
+  VirtualCookieStore
+} from '@nano_kit/platform-web'
+
+const cookieStore = new VirtualCookieStore(
+  'theme=dark; session=abc123',
+  '/dashboard'
+)
+
+const context = new InjectionContext([
+  provide(CookieStore$, cookieStore)
+])
+
+await cookieStore.set({
+  name: 'theme',
+  value: 'light',
+  path: '/',
+  sameSite: 'lax'
+})
+
+cookieStore.peek('theme') // 'light'
+cookieStore.drainSetCookieHeaders()
+// ['theme=light; Path=/; SameSite=Lax']
+```
+
 ## Broadcast Channel
 
 `broadcasted` creates a signal synchronized through `BroadcastChannel`. It is useful for transient cross-tab messages such as logout, refresh, or UI coordination events.
@@ -233,3 +286,45 @@ $authEvent('logout')
 ```
 
 `broadcasted` supports the same default value, [codec](/store/advanced/#codecs), and [setter rate limiter](/store/advanced/#rate-limiting) overloads as the storage helpers.
+
+## Locale
+
+`browserLocale` picks the best locale from a browser-like language container. In the browser, pass `navigator` directly.
+
+```ts
+import { browserLocale } from '@nano_kit/platform-web'
+
+const locale = browserLocale(navigator, ['en', 'ru'], 'en')
+```
+
+For universal code, use the `Locales$` injection token. By default it returns `navigator`, so browser-only code does not need any setup.
+
+```ts
+import { inject } from '@nano_kit/store'
+import {
+  Locales$,
+  browserLocale
+} from '@nano_kit/platform-web'
+
+export function Locale$() {
+  const locales = inject(Locales$)
+
+  return browserLocale(locales, ['en', 'ru'], 'en')
+}
+```
+
+On the server, provide `Locales$` with `parseLocales(...)` from the request `Accept-Language` header.
+
+```ts
+import { provide } from '@nano_kit/store'
+import {
+  Locales$,
+  parseLocales
+} from '@nano_kit/platform-web'
+
+const context = [
+  provide(Locales$, parseLocales(request.headers.get('accept-language')))
+]
+```
+
+`parseLocales` sorts languages by `q` quality and keeps declaration order when qualities are equal. Empty headers fall back to `{ language: 'en', languages: ['en'] }`.
diff --git a/website/src/content/docs/router/advanced.mdx b/website/src/content/docs/router/advanced.mdx
index 1c0e9456..e5814c91 100644
--- a/website/src/content/docs/router/advanced.mdx
+++ b/website/src/content/docs/router/advanced.mdx
@@ -376,15 +376,3 @@ declare module '@nano_kit/router' {
 - **`component`** — your framework's component type (e.g. `() => ReactNode`). Enables typed `$page().default` in `Page$`.
 
 If `AppContext` is not extended, all tokens fall back to generic types.
-
-### `virtualNavigationContext`
-
-`virtualNavigationContext` creates an `InjectionContext` pre-configured with a virtual (in-memory) navigation. It is a shorthand for creating a context with `virtualNavigation` + `provide`. Useful for SSR and testing.
-
-```ts
-import { virtualNavigationContext } from '@nano_kit/router'
-import { routes } from './routes'
-
-const context = virtualNavigationContext('/users/123', routes)
-/* context already has Location$ and Navigation$ provided */
-```
diff --git a/website/src/content/docs/router/testing.mdx b/website/src/content/docs/router/testing.mdx
index 88dbc54d..319a51c4 100644
--- a/website/src/content/docs/router/testing.mdx
+++ b/website/src/content/docs/router/testing.mdx
@@ -42,23 +42,3 @@ it('should render the admin page', async () => {
   expect(screen.getByText('Admin Panel')).toBeInTheDocument()
 })
 ```
-
-Alternatively, use `virtualNavigationContext` as a shorthand — it creates the context and provides both tokens for you:
-
-```tsx
-import { virtualNavigationContext } from '@nano_kit/router'
-import { routes } from './routes'
-import { App } from './App'
-
-it('should render the home page', async () => {
-  const context = virtualNavigationContext('/', routes)
-
-  render(
-    <InjectionContextProvider context={context}>
-      <App />
-    </InjectionContextProvider>
-  )
-
-  expect(screen.getByText('Home')).toBeInTheDocument()
-})
-```
diff --git a/website/src/content/docs/ssr/cookies.mdx b/website/src/content/docs/ssr/cookies.mdx
index 48d85546..e5bb460e 100644
--- a/website/src/content/docs/ssr/cookies.mdx
+++ b/website/src/content/docs/ssr/cookies.mdx
@@ -1,29 +1,29 @@
 ---
 title: Cookies
-description: "Use request cookies during Nano Kit SSR with @nano_kit/cookie-store."
+description: "Use request cookies during Nano Kit SSR with @nano_kit/platform-web."
 sidebar:
   order: 2
 ---
 
 import { Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components'
 
-`@nano_kit/cookie-store` provides a request-bound, [`CookieStore`](https://developer.mozilla.org/en-US/docs/Web/API/Cookie_Store_API)-compatible implementation for SSR and tests.
+`@nano_kit/platform-web` provides a request-bound, [`CookieStore`](https://developer.mozilla.org/en-US/docs/Web/API/Cookie_Store_API)-compatible implementation for SSR and tests.
 
 Use it when server-rendered code needs to read incoming cookies, write `Set-Cookie` headers, or provide cookie state through Nano Kit dependency injection. You can use it directly through the [`CookieStore` API](https://developer.mozilla.org/en-US/docs/Web/API/Cookie_Store_API), or combine it with [`cookieStored`](/platform/web/#cookies) from `@nano_kit/platform-web` when you want cookie-backed signals.
 
 ## Installation
 
-`@nano_kit/cookie-store` is an optional peer dependency of `@nano_kit/ssr`. Install it only when your SSR app uses cookies.
+`@nano_kit/platform-web` is an optional peer dependency of `@nano_kit/ssr`. Install it only when your SSR app uses cookies.
 
 <Tabs syncKey='pkg'>
   <TabItem label='pnpm' icon='pnpm'>
-    <Code frame='none' lang='bash' code='pnpm add @nano_kit/cookie-store' />
+    <Code frame='none' lang='bash' code='pnpm add @nano_kit/platform-web' />
   </TabItem>
   <TabItem label='Yarn' icon='seti:yarn'>
-    <Code frame='none' lang='bash' code='yarn add @nano_kit/cookie-store' />
+    <Code frame='none' lang='bash' code='yarn add @nano_kit/platform-web' />
   </TabItem>
   <TabItem label='npm' icon='seti:npm'>
-    <Code frame='none' lang='bash' code='npm install @nano_kit/cookie-store' />
+    <Code frame='none' lang='bash' code='npm install @nano_kit/platform-web' />
   </TabItem>
 </Tabs>
 
@@ -51,7 +51,7 @@ export default defineConfig({
 The option makes the renderer create a `VirtualCookieStore` for each request and provide it through `CookieStore$`.
 
 <Aside>
-  `cookieStore: true` requires `@nano_kit/cookie-store` to be installed. Keep the option disabled when the app does not read or write cookies during SSR.
+  `cookieStore: true` requires `@nano_kit/platform-web` to be installed. Keep the option disabled when the app does not read or write cookies during SSR.
 </Aside>
 
 ## Direct Cookie Store Usage
@@ -61,7 +61,7 @@ Read `CookieStore$` inside a store factory when you want to work with the [`Cook
 ```ts
 // src/stores/session.ts
 import { action, inject } from '@nano_kit/store'
-import { CookieStore$ } from '@nano_kit/cookie-store'
+import { CookieStore$ } from '@nano_kit/platform-web'
 
 const SESSION_MAX_AGE = 60 * 60 * 24 * 30
 
@@ -105,8 +105,10 @@ If you want a writable signal backed by cookies, pass the injected `CookieStore$
 ```ts
 // src/stores/session.ts
 import { action, inject } from '@nano_kit/store'
-import { CookieStore$ } from '@nano_kit/cookie-store'
-import { cookieStored } from '@nano_kit/platform-web'
+import {
+  CookieStore$,
+  cookieStored
+} from '@nano_kit/platform-web'
 
 const SESSION_MAX_AGE = 60 * 60 * 24 * 30
 
@@ -139,14 +141,16 @@ export function Session$() {
 
 ## Production Server
 
-Pass the incoming `Cookie` header to `renderer.render(url, cookieHeader)`, and forward returned `Set-Cookie` headers to the HTTP response.
+Pass the incoming `Cookie` header to `renderer.render(url, { cookie })`, and forward returned `Set-Cookie` headers to the HTTP response.
 
 ```js
 // server.js
 import { renderer } from './dist/renderer/index.js'
 
 app.get('*', async (req, res) => {
-  const result = await renderer.render(req.url, req.headers.cookie)
+  const result = await renderer.render(req.url, {
+    cookie: req.headers.cookie
+  })
 
   if (result.setCookieHeaders) {
     res.setHeader('Set-Cookie', result.setCookieHeaders)
@@ -200,7 +204,7 @@ import { InjectionContext, provide } from '@nano_kit/store'
 import {
   CookieStore$,
   VirtualCookieStore
-} from '@nano_kit/cookie-store'
+} from '@nano_kit/platform-web'
 
 const cookieStore = new VirtualCookieStore(
   'theme=dark; session=abc123',
diff --git a/website/src/content/docs/ssr/index.mdx b/website/src/content/docs/ssr/index.mdx
index 13e8afc0..55190fa3 100644
--- a/website/src/content/docs/ssr/index.mdx
+++ b/website/src/content/docs/ssr/index.mdx
@@ -187,7 +187,13 @@ export default defineConfig({
 })
 ```
 
-Use `cookieStore: true` when the renderer should provide a request-bound `CookieStore$` during SSR. This feature uses the optional peer package `@nano_kit/cookie-store`, so install it in the app before enabling the option. See [SSR Cookies](/ssr/cookies) for the full setup, including store code and `Set-Cookie` forwarding.
+### SSR Options
+
+The SSR plugin can provide request-bound browser-like dependencies for stores that run during server rendering.
+
+#### `cookieStore`
+
+Use `cookieStore: true` when the renderer should provide a request-bound `CookieStore$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. See [SSR Cookies](/ssr/cookies) for the full setup, including store code and `Set-Cookie` forwarding.
 
 ```js
 ssr({
@@ -196,6 +202,19 @@ ssr({
 })
 ```
 
+#### `browserLocale`
+
+Use `browserLocale: true` when the renderer should provide request-bound `Locales$` during SSR. This feature uses the optional peer package `@nano_kit/platform-web`, so install it in the app before enabling the option. The renderer parses the incoming `Accept-Language` header with [`parseLocales`](/platform/web/#locale), so universal stores can inject `Locales$` and resolve the same locale shape on the server and in the browser. See [SSR Locale](/ssr/locale) for the full setup.
+
+```js
+ssr({
+  index: 'src/index.js',
+  browserLocale: true
+})
+```
+
+### Build and Serve
+
 - **`vite dev`** — starts the development server with SSR rendering handled in-process via Vite's dev middleware.
 - **`vite build`** — produces two output directories: `dist/client/` (browser assets) and `dist/renderer/` (SSR renderer bundle).
 
@@ -228,5 +247,5 @@ app.get('*', async (req, res) => {
 
 - [`@nano_kit/react-ssr`](/integrations/react-ssr) — The React adapter built with this package.
 - [`@nano_kit/preact-ssr`](/integrations/preact-ssr) — The Preact adapter built with this package.
-- [SSR Cookies](/ssr/cookies) — Request-bound cookie stores and `cookieStore: true`.
+- [SSR Cookies](/ssr/cookies) — Request-bound cookie stores.
 - [Router SSR](/router/ssr) — [`Stores$`](/router/ssr#stores-data-dehydration), [`Head$`](/router/ssr#head-management), and other page-level SSR hooks.
diff --git a/website/src/content/docs/ssr/locale.mdx b/website/src/content/docs/ssr/locale.mdx
new file mode 100644
index 00000000..09bedf42
--- /dev/null
+++ b/website/src/content/docs/ssr/locale.mdx
@@ -0,0 +1,131 @@
+---
+title: Locale
+description: "Use request locales during Nano Kit SSR with @nano_kit/platform-web."
+sidebar:
+  order: 3
+---
+
+import { Tabs, TabItem, Code, Aside } from '@astrojs/starlight/components'
+
+`@nano_kit/platform-web` provides browser-like locale helpers for SSR and tests.
+
+Use them when server-rendered code needs to resolve the user's preferred locale from the incoming `Accept-Language` header, or provide locale state through Nano Kit dependency injection. You can use [`browserLocale`](/platform/web/#locale) directly with `navigator`, or combine `Locales$` with `parseLocales` when the same store should work in both the browser and SSR.
+
+## Installation
+
+`@nano_kit/platform-web` is an optional peer dependency of `@nano_kit/ssr`. Install it only when your SSR app uses request-bound browser helpers such as `Locales$`.
+
+<Tabs syncKey='pkg'>
+  <TabItem label='pnpm' icon='pnpm'>
+    <Code frame='none' lang='bash' code='pnpm add @nano_kit/platform-web' />
+  </TabItem>
+  <TabItem label='Yarn' icon='seti:yarn'>
+    <Code frame='none' lang='bash' code='yarn add @nano_kit/platform-web' />
+  </TabItem>
+  <TabItem label='npm' icon='seti:npm'>
+    <Code frame='none' lang='bash' code='npm install @nano_kit/platform-web' />
+  </TabItem>
+</Tabs>
+
+## Vite Plugin
+
+Enable request-bound locale containers with the SSR plugin option:
+
+```ts
+// vite.config.ts
+import { defineConfig } from 'vite'
+import react from '@vitejs/plugin-react'
+import ssr from '@nano_kit/react-ssr/vite-plugin'
+
+export default defineConfig({
+  plugins: [
+    react(),
+    ssr({
+      index: 'src/index.tsx',
+      browserLocale: true
+    })
+  ]
+})
+```
+
+The option makes the renderer parse the incoming `Accept-Language` header and provide the result through `Locales$`.
+
+<Aside>
+  `browserLocale: true` requires `@nano_kit/platform-web` to be installed. Keep the option disabled when the app does not resolve locale during SSR.
+</Aside>
+
+## Usage
+
+Read `Locales$` inside a store factory when you want to resolve the current locale from the context.
+
+```ts
+// src/stores/locale.ts
+import { inject } from '@nano_kit/store'
+import {
+  Locales$,
+  browserLocale
+} from '@nano_kit/platform-web'
+
+const SUPPORTED_LOCALES = ['en', 'ru'] as const
+
+export function Locale$() {
+  const locales = inject(Locales$)
+  const locale = browserLocale(locales, SUPPORTED_LOCALES, 'en')
+
+  return {
+    locale
+  }
+}
+```
+
+In the browser, `Locales$` resolves to `navigator`. During SSR, it resolves to a parsed `Accept-Language` container for the current request.
+
+## Production Server
+
+Pass the incoming `Accept-Language` header to `renderer.render(url, { acceptLanguage })`.
+
+```js
+// server.js
+import { renderer } from './dist/renderer/index.js'
+
+app.get('*', async (req, res) => {
+  const result = await renderer.render(req.url, {
+    acceptLanguage: req.headers['accept-language']
+  })
+
+  if (result.redirect) {
+    return res.redirect(result.statusCode, result.redirect)
+  }
+
+  if (result.html !== null) {
+    return res.status(result.statusCode).send(result.html)
+  }
+
+  res.status(result.statusCode).send('Not Found')
+})
+```
+
+The Vite dev server passes this header automatically when `browserLocale: true` is enabled.
+
+## Low-Level Usage
+
+You can also use `parseLocales` directly in tests or custom render pipelines:
+
+```ts
+import { InjectionContext, provide } from '@nano_kit/store'
+import {
+  Locales$,
+  browserLocale,
+  parseLocales
+} from '@nano_kit/platform-web'
+
+const locales = parseLocales('ru-RU,ru;q=0.9,en-US;q=0.8,en;q=0.7')
+const context = new InjectionContext([
+  provide(Locales$, locales)
+])
+
+browserLocale(context.get(Locales$), ['en', 'ru-RU'], 'en')
+// 'ru-RU'
+```
+
+`parseLocales` sorts languages by `q` quality and keeps declaration order when qualities are equal. Empty headers fall back to `{ language: 'en', languages: ['en'] }`.
diff --git a/website/src/content/docs/store/advanced.mdx b/website/src/content/docs/store/advanced.mdx
index 26b22dd7..8e92ba8d 100644
--- a/website/src/content/docs/store/advanced.mdx
+++ b/website/src/content/docs/store/advanced.mdx
@@ -429,7 +429,7 @@ function getPosition(options?: PositionOptions) {
 
 const $highAccuracy = signal(false)
 const [$position, $error, $pending] = resolved(
-  computed(() => getPosition({ enableHighAccuracy: $highAccuracy() }))
+  () => getPosition({ enableHighAccuracy: $highAccuracy() })
 )
 ```
 
diff --git a/website/src/content/docs/store/ssr.mdx b/website/src/content/docs/store/ssr.mdx
index 32f0c41c..d0f7f7c3 100644
--- a/website/src/content/docs/store/ssr.mdx
+++ b/website/src/content/docs/store/ssr.mdx
@@ -140,14 +140,22 @@ const dehydrated = await dehydrate(() => {
 ```
 
 The `dehydrate` function:
-1. Creates an injection context with a task pool
+1. Creates an injection context with a task pool, or uses the context passed as the second argument
 2. Runs your store factories within that context
 3. Starts effects to trigger `onMount` callbacks (which start async tasks)
 4. Waits for all tasks in `TasksPool$` to complete
 5. Collects all signals marked with `hydratable`
 6. Returns the dehydrated key-value pairs
 
-If you also need access to the injection context (e.g. for additional SSR work), use `contextDehydrate` — it returns `[context, dehydrated]` instead.
+If your stores need preconfigured dependencies, pass them as the second argument. It can be an `InjectionContext` instance or an array of providers for a new context.
+
+```ts
+import { dehydrate, provide } from '@nano_kit/store'
+
+const dehydrated = await dehydrate(Stores$, [
+  provide(UserId$, 1)
+])
+```
 
 ### Client-Side Hydration