Windsurf storage

Blob Storage Corrupting Uploaded Files in Windsurf App

Files uploaded to blob storage through your Windsurf-generated app become corrupted when downloaded. PDFs are unreadable, images show garbled data, ZIP files fail to extract, and documents open as random characters. The upload appears to succeed, but the stored file is damaged.

This is a particularly insidious bug because uploads appear successful — no errors are thrown, the file shows up in storage, and the file size may even look correct. But when a user downloads and opens the file, it's broken.

The corruption typically affects binary files (images, PDFs, ZIPs) while text files may work fine, which is a strong clue that the issue is related to encoding or stream handling.

Error Messages You Might See

Error: Invalid or corrupted PDF Failed to decode image Error: End-of-central-directory signature not found (ZIP) The file is damaged and could not be opened UTF-8 decode error on binary data
Error: Invalid or corrupted PDFFailed to decode imageError: End-of-central-directory signature not found (ZIP)The file is damaged and could not be openedUTF-8 decode error on binary data

Common Causes

  • UTF-8 encoding applied to binary data — Cascade read the file as a UTF-8 string instead of a Buffer, destroying binary data during encoding conversion
  • Base64 double-encoding — The file is base64-encoded before upload, but the storage client also encodes it, resulting in double-encoded data
  • Wrong content-type on upload — The file is uploaded with content-type: text/plain or application/json instead of its actual MIME type
  • Stream not piped correctly — The readable stream is consumed (read to string) before being passed to the storage upload, instead of being piped directly
  • Multipart boundary parsing error — The multipart form parser mishandles the file boundaries, truncating or appending extra bytes

How to Fix It

  1. Always use Buffer for binary files — Never call toString() on file data. Use Buffer objects or ArrayBuffer throughout the upload pipeline
  2. Set the correct content-type — Detect the MIME type using the file-type library or the upload's mimetype field, and pass it to the storage upload call
  3. Avoid double-encoding — Check if your storage client already handles encoding. Don't base64-encode if the client expects a Buffer or stream
  4. Pipe streams directly — Instead of reading the entire file into memory, pipe the upload stream directly to the storage write stream
  5. Verify with checksums — Generate an MD5 hash before upload and after download to confirm the file is identical. If hashes differ, the corruption is in the upload path
  6. Test with binary files specifically — Upload a small PNG or PDF and download it immediately. Open it to verify integrity before shipping to production

Real developers can help you.

Matthew Butler Matthew Butler Systems Development Engineer @ Amazon Web Services Caio Rodrigues 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.** Kingsley Omage Kingsley Omage Fullstack software engineer passionate about AI Agents, blockchain, LLMs. Matt Butler Matt Butler Software Engineer @ AWS MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. Tejas Chokhawala Tejas Chokhawala Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript. Focused on performance, clean architecture and shipping fast. Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools. Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups legrab legrab I'll fill this later Rudra Bhikadiya 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.

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 text files upload fine but images get corrupted?

Text files survive UTF-8 encoding because they're already text. Binary files (images, PDFs, ZIPs) contain byte sequences that are invalid UTF-8, so encoding them as strings destroys the data. Always handle binary files as Buffers.

How can I tell if corruption happens during upload or download?

Check the file directly in your storage dashboard (S3 console, Supabase dashboard). Download it from there. If it's corrupt in storage, the upload is the problem. If it's fine in storage but corrupt when downloaded through your app, the download handler is the issue.

Related Windsurf 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