Expo Svelte
GitHub
src/routes/+mobile.svelte
<script lang="ts">
	import { SafeAreaView, Screen, ScrollView, Text } from 'expo-svelte';
</script>

<Screen title="Settings">
	<SafeAreaView edges={['left', 'right', 'bottom']} style={{ flex: 1 }}>
		<ScrollView contentContainerStyle={{ padding: 20, gap: 12 }}>
			<Text>The last row stays above the home indicator.</Text>
		</ScrollView>
	</SafeAreaView>
</Screen>

Props

Prop Type Default Description
edges readonly ('top' | 'right' | 'bottom' | 'left')[] all four The edges to pad.
style ViewStyle As a View's. On each padded edge, the inset is added to the style's own padding.
class ClassValue A list of classes: a string, an array or an object, as on a DOM element in Svelte. Their style goes under style, which wins. Needs the css option (Classes).
children Snippet The content.

It also takes the props of View.

Which edges

Pad only the edges nothing else covers:

  • A screen with a header: the header already covers the top inset. Use ['left', 'right', 'bottom'].
  • A screen in a tab pane: the tab bar covers the bottom inset too. Use ['left', 'right'].
  • A screen without a header, or the content of a Modal: all four.
  • A screen with a toolbar: the toolbar covers the bottom inset. Leave 'bottom' out.

The left and right insets matter in landscape, on phones with a notch.

The insets store

The insets are also a reactive store, insets, for when you need a number instead of padding: the bottom padding of a scroll view's content, say.

svelte
<script lang="ts">
	import { ScrollView, insets } from 'expo-svelte';
</script>

<ScrollView contentContainerStyle={{ padding: 20, paddingBottom: 20 + insets.bottom }}>
	<!-- ... -->
</ScrollView>
Field Description
top, right, bottom, left The safe-area insets, in points.
keyboardVisible Whether the keyboard is open.
keyboardHeight How much of the screen the keyboard covers, in points.
frame The app's frame: { x, y, width, height }.

A template or $derived that reads a field updates when it changes: on rotation, or when the keyboard opens and closes. The store starts listening the first time a Screen, a SafeAreaView or connectInsets() (also exported) runs, so in an app with screens it's always live.

Type to search the guide.