v0 storage

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

GET /images/logo.png 404 (Not Found) Failed to load resource: the server responded with a status of 404 Module not found: Can't resolve './assets/image.png' @font-face failed to load: 404
GET /images/logo.png 404 (Not Found)Failed to load resource: the server responded with a status of 404Module not found: Can't resolve './assets/image.png'@font-face failed to load: 404

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

  1. Use absolute paths — reference all static assets with leading slash: /images/logo.png not ./images/logo.png
  2. Check case sensitivity — ensure filenames match exactly including capitalization: Logo.PNG vs logo.png
  3. Verify public folder structure — all static assets must be in the /public directory at the project root
  4. Check .gitignore — ensure static assets are not being excluded from version control and deployment
  5. Use next/font for fonts — replace public folder fonts with next/font/google or next/font/local for automatic optimization
  6. Test with production build — run next build && next start locally to catch asset issues before deploying

Real developers can help you.

Victor Denisov Victor Denisov Developer Milan Surelia Milan Surelia Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems. Expertise: 💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web. 🖋️ Sharing insights through technical writing, blogging, and open-source contributions. 🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences. Notable Achievements: 🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX. 🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development. 🌟 Open source contributions on Github & StackOverflow for Flutter & Dart 🎖️ Worked on improving app performance and user experience with smart solutions. Milan is always happy to connect, work on new ideas, and explore the latest in technology. prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Stanislav Prigodich Stanislav Prigodich 15+ years building iOS and web apps at startups and enterprise companies. I want to use that experience to help builders ship real products - when something breaks, I'm here to fix it. Jen Jacobsen Jen Jacobsen I’m a Full-Stack Developer with over 10 years of experience building modern web and mobile applications. I enjoy working across the full product lifecycle — turning ideas into real, well-built products that are intuitive for users and scalable for businesses. I particularly enjoy building mobile apps, modern web platforms, and solving complex technical problems in a way that keeps systems clean, reliable, and easy to maintain. Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last. Kingsley Omage Kingsley Omage Fullstack software engineer passionate about AI Agents, blockchain, LLMs. Nam Tran Nam Tran 10 years as fullstack developer legrab legrab I'll fill this later Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

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

Related v0 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help