Route used params.x — params should be awaited Next.js Origin: On your device Last updated 5 Nov 2026

Next.js 15: Error: Route "/blog/[slug]" used `params.slug`. `params` should be awaited before using its properties

In Next.js 15 params and searchParams are Promises; reading properties synchronously triggers this error/warning.

Exact message you may see Route "/blog/[slug]" used `params.slug`. `params` should be awaited before using its propertiesError: Route used `params.id`. `params` should be awaited before using its properties`params` should be awaited before using its propertiesRoute used `searchParams.q`. `searchParams` should be awaitedsync-dynamic-apis params
Explore the map of this error Full error map →
Seen on: Next.js React

Meaning

Make the page/layout/route handler async and await params: const { slug } = await params. In Client Components use React.use(params). A codemod helps: npx @next/codemod@canary next-async-request-api .. Same for cookies(), headers() and draftMode().

Common causes

  • Upgrading to Next.js 15 without migration
  • Typing params as an object not a Promise
  • Route handlers using context.params.id
  • generateMetadata reading params synchronously
  • Client Component reading params directly

⚡ Quick fix

  1. export default async function Page({ params }: { params: Promise<{ slug: string }> }) { const { slug } = await params; }
  2. Client: const { slug } = use(params)
  3. Run the async-request-api codemod

Detailed fix by platform

Next.js

  1. npx @next/codemod@canary next-async-request-api .

How to diagnose

  1. Version — Next 15+?
  2. Types — Promise<...>?
  3. Context — Server or client?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

Conflicting app and page file was found — Next.js: ⨯ Conflicting app and page file was found, please remove the conflicting files to continue: "pages/index.tsx" - "app/page.tsx" (Next.js)Conflicting app and p…cookies() should be awaited — Next.js 15: Route "/x" used `cookies().get('token')`. `cookies()` should be awaited before using its value (Next.js)cookies() should be a…CORS error calling Next.js API route / route handler — Browser: Access to fetch at 'https://api.example.com/api/data' from origin 'https://app.example.com' has been blocked by CORS policy (Next.js route handler) (Next.js)CORS error calling Ne…next build: fetch failed ECONNREFUSED (build-time API) — Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 } (Next.js)next build: fetch fai…next build: JavaScript heap out of memory — Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build) (Next.js)next build: JavaScrip…searchParams should be awaited (Next.js 15) — Next.js 15: Route "/search" used `searchParams.q`. `searchParams` should be awaited (Next.js)searchParams should b…Type error during next build — Next.js: Failed to compile. ./src/app/page.tsx:15:9 Type error: Type 'string | undefined' is not assignable to type 'string' (Next.js)Type error during nex…useSearchParams() should be wrapped in a suspense boundary — Next.js: useSearchParams() should be wrapped in a suspense boundary at page "/". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout (Next.js)useSearchParams() sho…Route use…

Explore the map of this error Full error map →

🧠 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.