# Separate session lifetimes for native apps

[Native sessions](https://clerk.com/docs/guides/secure/session-options.md#native-sessions) are sessions created by:

- iOS and Android apps, including Expo apps
- Electron apps
- Chrome extensions, on production instances only, except extensions that [sync authentication with a web app](https://clerk.com/docs/guides/sessions/sync-host.md)

By default, native sessions follow the web browser settings, as they did before. You can set a custom maximum lifetime between 5 minutes and 10 years. Native sessions then use it instead of the web maximum lifetime and inactivity timeout. Session tokens stay short-lived, and SDKs keep refreshing them.

> A custom native lifetime is free in development instances. In production, your application needs the Pro or Business plan. See the [pricing page](https://clerk.com/pricing) for details.

Changes only apply to sessions created after you save. Existing sessions keep the lifetime they were created with. To end them sooner, [revoke them](https://clerk.com/docs/guides/secure/session-options.md#changes-to-existing-sessions).

## Get started

You don't need to update your SDK.

1. In the Clerk Dashboard, navigate to the [**Sessions**](https://dashboard.clerk.com/~/sessions) page.
2. Under **Native sessions**, select **Custom maximum lifetime** and set a duration.
3. Select **Save**.

To make native sessions follow the web browser settings again, select **Same as web**, then select **Save**. See [native session lifetime settings](https://clerk.com/docs/guides/secure/session-options.md#configure-a-separate-native-lifetime) for details.