Can catch-all segments contain static nested routes? ([...slug]/stats)

[7IBO]

Question

I'm trying to create a routing structure similar to npm's package pages, where I need to handle:

• Package names: /next, /@clerk/nextjs
• Nested routes for each package: /next/stats, /@clerk/nextjs/stats, /next/home, etc.

Proposed file structure

app/
└── [...slug]/
    ├── page.tsx          // For /next, /@clerk/nextjs
    ├── stats/
    │   └── page.tsx      // For /next/stats, /@clerk/nextjs/stats
    └── home/
        └── page.tsx      // For /next/home, /@clerk/nextjs/home

My understanding

Based on the documentation about catch-all segments, I know that:

• [...slug] captures multiple path segments as an array
• Static routes have priority over dynamic routes

However, I couldn't find clear documentation about whether static routes can be nested inside a catch-all segment folder.

Questions

1. Is this structure officially supported in Next.js App Router?
2. Will the static routes (stats/, home/) take precedence over the catch-all?
3. Are there any limitations or gotchas I should be aware of?

Additional context

I found conflicting information suggesting that catch-all segments "must be at the end" and cannot contain other folders, but I'm not sure if this applies to static routes or only to other dynamic segments.

Any clarification would be greatly appreciated!

[phokin4720]

Yes, catch-all routes can have static nested routes. For example, [...slug]/stats will match URLs like /blog/2025/post/stats with [...slug] catching the preceding segments and stats as a static nested page.