Expo Router v1 Release Candidate
January 19, 2023
The First File-Based Router for Native Apps!
The future of native navigation is here, and it's file-based! With the new Expo Router v1 (Release Candidate), pages are automatically generated by simply creating files in your project. You can focus on building the content of your pages rather than wrestling with all the boilerplate required to compose pages together. Try it out for yourself and see just how fast and easy, truly native development can be!
Get started today with one line:


𝝠 npx create-expo-app -e with-router
See the advanced setup for more.


Expo Router defines routes using file names and directories inside the root app/ directory:
  • Basic Routes β€” automatically add pages to your app. The route matches the name of the file, e.g. home.js becomes /home
  • Layout Routes β€” _layout.js file in any directory, will wrap all the children in the given directory. This can be used to create shared UI elements like headers and tab bars. Expo Router includes three default navigator components from React Navigation: Stack, Tabs, Navigator. Learn more in Expo Router: Native Layouts.
  • Dynamic Routes β€” [slug].js enables variable matching of a segment. Useful for posts, content, user profiles, etc. Adding the ... rest operator will match multiple segment levels.
  • Group Routes β€” (group)/ wrapping a directory in parentheses will skip adding a segment to the URL. Learn more in Expo Router: Groups.
  • Shared Routes β€” present different components simultaneously while leveraging the same URL for both. Useful for user profiles, or other content which can be accessed from multiple tabs in-app.
Learn more in Expo Router: Routing.


With Expo Router you move between pages using URLs and a <Link /> component. Dynamic routes automatically push screens according to the slug.
Learn more in Expo Router: Linking.

Metro for Web

To make Expo Router fully universal, we added web support to the Metro Bundler. This enables developers to use a single dev server, port, URL, and config for iOS, Android, and the web! Error messages, warnings, and the developer experience are now substantially more unified across platforms. Metro for web includes the following features:
  • Fast Refresh β€” it's really fast!
  • Automatic React Native web aliasing.
  • Expo SDK support β€” expo-constants manifest.
  • Unified LogBox Errors and stack trace symbolication.
  • SPA-styled exporting with npx expo export β€” pending more advanced rendering patterns.
Building Metro for web is part of our larger commitment, at Expo, to improve the Metro bundler across all platforms. Special thanks to the Metro team at Meta for their extensive support in this.
Learn more in Metro for web.

404s & Sitemap

Expo Router automatically handles missing routes to ensure a resilient user experience by default, this can be customized using dynamic routes.

Splash Screen

Expo Router automatically controls splash screen visibility while the navigation UI is rendering, preventing the β€œwhite flash” from ever showing, learn more.

Navigation Reimagined

Even though Expo Router leverages our powerful React Navigation suite, we've unified how many core routing concepts work across web and native. For example, instead of rehydrating complex state objects on native, you can redirect to a URL to achieve the same result.

Release Candidacy

This is a mostly-stable release of Expo Router which we will promote to v1 after it's been user tested for bugs. New major features will not be added until v2 work begins.
Expo Router v1 proves that file-based routing for native apps is not only possible, but also an incredibly powerful, scaleable, and enjoyable system! We will be releasing the stable v1 with Expo SDK 48, or earlier!
Report any bugs on the expo/router repo. See the demo todo list app for ideas of what's possible!

Known Issues

Below is a list of currently known issues or feature requests we haven't resolved as of v1:
  • Limited documentation: The API is still actively being worked on so we haven't documented the router with the level of finesse that one might expect from Expo docs. Testing, types, and exhaustive examples are not documented.
  • Automatic TypeScript types: We will be adding a number of automated types to Expo Router, however, this is not a priority for v1.
  • The convention is not ready for advanced use cases such as matching characters that cannot be expressed in a file name.
  • Server-based patterns: patterns like server-protected routes (authentication) are partially emulated in runtime space, but they aren't as expressive as we'd like them to be.
  • There currently exists no system for statically defining incoming URL rewrites.
ΒΉ Web frameworks using file-based routing include SvelteKit, Next.js, and Remix.

Thanks for reading πŸ‘

evanbacon – Overview
Building 𝝠 Expo β€’ Follow me on Twitter for updates πŸ₯“
Follow on GitHub