Render profile information
Display a signed-in user's name or contact details.
Clerk · Class
User
The User object represents the current user associated with a Clerk session. It provides core identity, contact, and metadata information.
How it works
The User object models the current session's user and exposes basic identity data, contact methods, and metadata. Access it through the framework's Clerk integration, then account for loading and signed-out states before reading its fields.
Returns
The current User object, or undefined while the session is loading, or null when no session is active.
Key points
- User describes the principal attached to the active session.
- Use User for common profile and contact details.
- Metadata is divided into public, private, and unsafe categories.
- User is one of Clerk's core SDK objects and is related to Clerk and Session.
Common mistakes
- Treat null as signed out rather than as a loading state.
- Do not read user properties until the loading state has completed.
Example: Read the current user
import { useUser } from '@clerk/nextjs'
export default function Profile() {
const { user, isLoaded } = useUser()
if (!isLoaded) return <p>Loading…</p>
if (!user) return <p>Signed out</p>
return <p>Hello, {user.firstName ?? 'there'}!</p>
}Reads the currently signed-in user after Clerk finishes loading.
When to use it
Personalize the experience
Use public metadata to customize application UI.
Gate user-specific content
Inspect the current session's principal before showing protected content.
Interview questions
QWhat does Clerk's User object represent?
The User object represents the user associated with the current session. It contains basic information such as names, email addresses, phone numbers, and public, private, and unsafe metadata.
Follow-up: How do you distinguish loading from signed out? A loading user is undefined; after loading, no active session is represented by null.
QHow should an application safely read the current user?
Use the framework integration's user hook or object, wait until loading completes, and then check whether the value is present before accessing fields. This avoids treating an unresolved session as an anonymous user.
Follow-up: What should the UI render for each state? A loading indicator for undefined, signed-out content for null, and protected user content for a User object.
QWhat kinds of data does User expose?
The object includes identity and contact information together with public, private, and unsafe metadata. Which fields are available depends on the resource type and the SDK surface being used.
Follow-up: Why separate metadata categories? They provide different visibility and trust boundaries, so application code should not expose or trust every category identically.
Related
ClerkSessionUserResource