Bolt
storage
Image Compression and Optimization Not Working in Bolt App
Your Bolt.new application loads images at full resolution regardless of display size, causing slow page loads, excessive bandwidth usage, and poor Core Web Vitals scores. A 5MB profile photo is served at 4000x3000 pixels even though it's displayed at 100x100 on the page.
Bolt's AI typically generates basic img tags or stores images exactly as uploaded without any processing. This means a user uploading a 10MB DSLR photo gets that exact 10MB file served to every visitor, even on slow mobile connections.
The problem compounds quickly: a page with 20 user-uploaded images can require 50MB+ of downloads, making your app unusable on mobile and destroying your Google PageSpeed score. Image optimization is one of the biggest performance wins for any web application.
Error Messages You Might See
LCP (Largest Contentful Paint) exceeded 4 seconds
Warning: Image with src has no width or height
Error: sharp module not found in production
net::ERR_CONTENT_LENGTH_MISMATCH (large image transfer failed)
Common Causes
- No image processing on upload — Images are stored at original resolution and format without server-side resizing or compression
- Missing Next.js Image component — Using plain <img> tags instead of Next.js <Image> which provides automatic optimization
- No lazy loading — All images load eagerly on page load, even those below the fold that aren't visible yet
- Wrong image format — Serving PNG or JPEG instead of modern WebP or AVIF formats that are 30-50% smaller
- No responsive sizing — Serving the same large image regardless of the user's screen size or viewport
How to Fix It
- Use Next.js Image component — Replace <img> with <Image> which auto-optimizes: <Image src={url} width={400} height={300} quality={80} />
- Compress on upload — Process images server-side before storage using sharp: sharp(buffer).resize(1200, 1200, { fit: 'inside' }).webp({ quality: 80 }).toBuffer()
- Use Supabase image transforms — Serve optimized images via transform URL: supabase.storage.from('images').getPublicUrl(path, { transform: { width: 400, quality: 80 } })
- Add lazy loading — Add loading="lazy" to images below the fold, or use the IntersectionObserver API for custom lazy loading
- Generate multiple sizes — Create thumbnail, medium, and full-size versions on upload and serve the appropriate one using srcset
- Set proper cache headers — Configure Cache-Control: public, max-age=31536000, immutable for static image assets
Real developers can help you.
Victor Denisov
Developer
Caio Rodrigues
I'm a full-stack developer focused on building practical and scalable web applications. My main experience is with **React, TypeScript, and modern frontend architectures**, where I prioritize clean code, component reusability, and maintainable project structures.
I have strong experience working with **dynamic forms, state management (Redux / React Hook Form), and complex data-driven interfaces**. I enjoy solving real-world problems by turning ideas into reliable software that companies can actually use in their daily operations.
Beyond coding, I care about **software quality and architecture**, following best practices for componentization, code organization, and performance optimization.
I'm also comfortable working across the stack when needed, integrating APIs, handling business logic, and helping transform prototypes into production-ready systems.
My goal is always to deliver solutions that are **simple, efficient, and genuinely useful for the people using them.**
Anthony Akpan
Developer with 8 years of experience building softwares fro startups
legrab
I'll fill this later
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
Matthew Butler
Systems Development Engineer @ Amazon Web Services
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
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.
Daniel Vázquez
Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting.
Meïr Ankri
Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
What image format should I use for web?
Use WebP as the default format - it provides 30% smaller files than JPEG at the same quality. For maximum compression, use AVIF (50% smaller than JPEG). Always provide a JPEG fallback for older browsers using the picture element.
How do I optimize images already in my storage bucket?
Use Supabase's built-in image transformation API to serve optimized versions without re-uploading. Add transform parameters to your getPublicUrl call: { transform: { width: 800, format: 'webp', quality: 75 } }.