Static Assets Returning 404 After Deployment
Static assets such as images, fonts, PDFs, and other files that work perfectly in local development return 404 errors after deploying your v0-generated Next.js app to Vercel. The public folder contents are not being served, or asset paths are resolving incorrectly in production.
This commonly happens because v0 generates references to assets using relative paths that work in development but break when the application is deployed under a base path or when the build output restructures the file hierarchy.
Fonts loaded from the public folder may also fail to load, causing layout shifts as the browser falls back to system fonts, and favicon or Open Graph images referenced in metadata may return 404 in production.
Error Messages You Might See
){kind=link}
Common Causes
- Case sensitivity mismatch — local filesystem (macOS/Windows) is case-insensitive but Vercel's Linux filesystem is case-sensitive
- Relative paths instead of absolute — using './images/logo.png' instead of '/images/logo.png' breaks after deployment
- Assets outside public folder — files placed in src/ or app/ directories are not served statically
- Build output not including assets — .gitignore or .vercelignore excluding necessary static files
- Base path not prepended — when using basePath in next.config.js, asset URLs need the prefix
How to Fix It
- Use absolute paths — reference all static assets with leading slash:
/images/logo.pngnot./images/logo.png - Check case sensitivity — ensure filenames match exactly including capitalization: Logo.PNG vs logo.png
- Verify public folder structure — all static assets must be in the /public directory at the project root
- Check .gitignore — ensure static assets are not being excluded from version control and deployment
- Use next/font for fonts — replace public folder fonts with next/font/google or next/font/local for automatic optimization
- Test with production build — run
next build && next startlocally to catch asset issues before deploying
Real developers can help you.
Nam Tran
10 years as fullstack developer
Omar Faruk
As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience.
My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture.
I played a key role in creating a scalable and maintainable platform to support educators and learners globally.
I'm enthusiastic about embracing new challenges and making meaningful contributions.
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
Rudra Bhikadiya
I build and fix web apps across Next.js, Node.js, and DBs.
Comfortable jumping into messy code, broken APIs, and mysterious bugs.
If your project works in theory but not in reality, I help close that gap.
Sage Fulcher
Hey I'm Sage! Im a Boston area software engineer who grew up in South Florida. Ive worked at a ton of cool places like a telehealth kidney care startup that took part in a billion dollar merger (Cricket health/Interwell health), a boutique design agency where I got to work on a ton of exciting startups including a photography education app, a collegiate Esports league and more (Philosophie), a data analytics as a service startup in Cambridge (MA) as well as at Phillips and MIT Lincoln Lab where I designed and developed novel network security visualizations and analytics. I've been writing code and furiously devoted to using computers to make people’s lives easier for about 17 years. My degree is in making computers make pretty lights and sounds. Outside of work I love hip hop, the Celtics, professional wrestling, magic the gathering, photography, drumming, and guitars (both making and playing them)
Costea Adrian
Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system.
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
Vlad Temian
15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox).
Cursor ambassador and agentic tooling builder.
I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti.
I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks.
https://blog.vtemian.com/
Richard McSorley
Full-Stack Software Engineer with 8+ years building high-performance applications for enterprise clients. Shipped production systems at Walmart (4,000+ stores), Cigna (20M+ users), and Arkansas Blue Cross. 5 patents in retail/supply chain tech. Currently focused on AI integrations, automation tools, and TypeScript-first architectures.
Kingsley Omage
Fullstack software engineer passionate about AI Agents, blockchain, LLMs.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why do my assets work locally but not on Vercel?
Most likely a case sensitivity issue. macOS and Windows filesystems are case-insensitive, but Vercel runs on Linux which is case-sensitive. Check that filenames match exactly.
Where should I put static files in Next.js?
Place them in the /public directory at your project root. They are served from the root URL: /public/logo.png is accessible at /logo.png.
How do I serve files from a subdirectory?
Create subdirectories inside /public. For example, /public/downloads/guide.pdf is accessible at /downloads/guide.pdf.