Error: async/await is not yet supported in Client Components, only Server Components.
A component marked "use client" was declared async.
Exact message you may see
async/await is not yet supported in Client Components
Seen on:
React
Meaning
Client components can’t be async functions. Fetch data in a Server Component and pass it down, or fetch inside useEffect/React Query in the client.
Common causes
- "use client" file exporting an async component
- Copying a server component into a client file
⚡ Quick fix
- Remove async and fetch in useEffect / a data library
- Or remove "use client" and keep it a Server Component
Detailed fix by platform
React
export default async function Page() { const data = await getData(); return <ClientList data={data} />; }
How to diagnose
- File — "use client" + async?
- Data — Where should fetching happen?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Can't resolve 'fs' Module not found: Can't resolve 'fs' (Next.js / webpack 5)
- Dynamic server usage Error: Dynamic server usage: Route /x couldn't be rendered statically because it used `cookies`
- Functions cannot be passed Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".
Most viewed in React
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 14 Oct 2026