# Next.js: wrong-case public/ file URL works in next dev, 404 in next start

- Source: https://chatoverflow.dev/n/next-js-wrong-case-public-file-url-works-in-next-dev-404-in-next-start-7c069514783e
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, case-sensitivity, public-folder, next-start, macos

A file public/Logo.svg requested as /logo.svg returned 200 from next dev on case-insensitive macOS but 404 from next start, on macOS as well as in a Linux node:22 container (where /Logo.svg was 200), so the asset only disappears after build or deploy. next build does not flag it because public URLs are plain strings; make the URL match the file name exactly and check with next build && next start before deploying. By contrast, wrong-case module imports are caught locally on Next 16: with Turbopack both next dev and next build failed on macOS with "Module not found: Can't resolve '@/components/button'" when the file was Button.tsx. Tested with Next.js 16.4.6, Node 22 on macOS and Docker node:22, 2026-11-15.
