Layouts

Define a wrapping component for routes at the same level or below using layouts:

'/about': {
	'/': About,
	'/work': Work,
	'/team': Team,
	layout: AboutLayout,
},

This layout component must render its children:

AboutLayout.svelte

<script lang="ts">
	import type { Snippet } from 'svelte';

	let { children }: { children: Snippet } = $props();
</script>

<div class="wrapper">
	{@render children()}
</div>

NOTE

When navigating between routes that share the same layout, the layout component persists without being recreated. This prevents unnecessary side effect triggers.

WARNING

Layouts can only be used in tree structure, which means that doing the following will not work:

'/about': About,
'/about/layout': AboutLayout, // ❌ Won't work

Break Out of Layouts

Sometimes you may want certain routes to ignore their parent's layout. You can exclude a route from inheriting its parent layout by wrapping the route segment in parentheses:

'/about': {
	'/': About, // Uses AboutLayout
	'/work': {
		"/": Work, // Uses AboutLayout
		"/(clients)": Clients, // Ignores AboutLayout
	},
	layout: AboutLayout,
},

This pattern works for all route types, including dynamic segments and catch-all routes:

// Dynamic route that ignores parent layout
"/(:id)": PostId,

// Catch-all route that ignores parent layout
"(*notfound)": NotFound,

This technique allows you to selectively bypass layouts while maintaining your overall route hierarchy.

Break Out to a Named Layout

To keep some layouts but not all of them, append @ followed by the name of the segment whose layout should be kept. Every layout below that segment is skipped:

'/about': {
	'/work': {

		'/': Work, // Uses RootLayout, AboutLayout and WorkLayout
		'/clients@about': Clients, // Uses RootLayout and AboutLayout
		'/archive@': Archive, // Uses RootLayout only
		layout: WorkLayout,
	},
	layout: AboutLayout,
},
layout: RootLayout,

A lone @ keeps only the root layout. This also works with index ('/@about'), dynamic ('/:id@about') and catch-all ('*rest@about') routes, and a dynamic segment can be targeted by its name ('/edit@:id').

If the name after @ is not one of the route's parent segments, the @ is treated as a regular character of the path (like '/@me').