# Routing in Clerk

Some of Clerk's components have their own internal routing.

For example, say a user uses their email address to fill out the [<SignUp />](https://clerk.com/docs/reference/components/authentication/sign-up.md) form. Once they submit the form, they are redirected from `/sign-up` to `/sign-up/verify-email-address`, which renders Clerk's UI for verifying a user's email address. This redirect is handled by Clerk's internal routing.

## `routing` prop

The following Clerk components accept a `routing` prop in order to define the routing strategy:

- [<SignUp />](https://clerk.com/docs/reference/components/authentication/sign-up.md)
- [<SignIn />](https://clerk.com/docs/reference/components/authentication/sign-in.md)
- [<UserProfile />](https://clerk.com/docs/reference/components/user/user-profile.md)
- [<CreateOrganization />](https://clerk.com/docs/reference/components/organization/create-organization.md)
- [<OrganizationProfile />](https://clerk.com/docs/reference/components/organization/organization-profile.md)

There following routing strategies can be passed:

- [`path`](#path-routing)
- [`hash`](#hash-routing)

Clerk will attempt to select the routing strategy that best integrates with your framework of choice. If for some reason the default routing strategy doesn't work for you, use the information below to pick a strategy that will work for your setup.

### `path` routing

`path` routing uses the path in the URL to determine the route. This is useful for server-rendered pages where SEO and server-side routing are crucial, such as Next.js applications.

For example, say you have a Clerk + Next.js application with the `<SignUp />` component on a dedicated `/sign-up` page. A user visit this page and uses their email address to fill out the `<SignUp />` form. Once they submit the form, they are redirected from `/sign-up` to `/sign-up/verify-email-address`.

For the following SDKs, `path` routing is set _by default_ on all Clerk components, as these frameworks support server-side routing out-of-the-box. There is no need to pass the `routing` or `path` props to Clerk components in these frameworks.

- Next.js
- TanStack React Start
- React Router

### `hash` routing

`hash` routing uses [the hash (#) portion of the URL](https://developer.mozilla.org/en-US/docs/Web/API/URL/hash) to determine the route. This is useful for single-page applications that use client-side routing.

For example, say you have a Clerk + React application with the `<SignUp />` component on a dedicated `/sign-up` page. A user visit this page and uses their email address to fill out the `<SignUp />` form. Once they submit the form, they are redirected from `/sign-up` to `/sign-up#verify-email-address`.

In Clerk applications that use any SDK other than [the ones listed in the previous section](#path-routing), `hash` routing is set _by default_ on all Clerk components.

---

## Sitemap

[Overview of all docs pages](https://clerk.com/docs/llms.txt)