[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # v0 project export missing generated image assets in downloaded archive 58 views · 0 likes · 2 posts d1maaz (@dimaazzchannel-6302) · 2026-02-08 After generating the project, the images are visible in the preview UI and appear to be present in folders, but when the project is downloaded as an archive, the folder containing the images is missing or the images are not included in the archive. Everything worked fine last week. Images were created, saved, and packaged into the downloaded archive without any issues. The problem arose suddenly today, without any changes on my part. ## Current Behavior - Images are visible during generation / preview - Image folders appear in the UI - After clicking `Download` / `Export`: - The image folder is missing from the archive - Or the image files do not physically exist in the downloaded project ## Expected Behavior - All images visible in the preview should exist as real image files and be included in the downloaded archive. ## Steps to Reproduce 1. Generate a project 2. Wait until images appear in the preview 3. Confirm images render correctly 4. Click `Download` / `Export` 5. Open the downloaded archive 6. Observe that the image folder is missing or empty ## Important Note These are not placeholder images. These are generated assets that: - Were included in the archive previously - Worked correctly last week - Were fully usable in the project ## Project Information - **Framework:** `Next.js` - Images are used as regular assets (not mocks) - The project previously exported images correctly - The issue appeared without any configuration changes [ image156×651 5.54 KB ](https://global.discourse-cdn.com/vercel/original/3X/c/d/cd4b05327593f3941b483f9001de397c76028721.png "image") [ 1690×425 63.9 KB ](https://global.discourse-cdn.com/vercel/original/3X/f/3/f3768d1833487f23ac77c9cd75a6f55df98ca694.jpeg "1") [ image663×817 39 KB ](https://global.discourse-cdn.com/vercel/original/3X/c/3/c3a2a722b848de6eb25e4a841ba184c0fbb5837f.png "image") Dev Shehzad (@dev-shehzad) · 2026-02-08 This is likely not a Next.js problem but how v0 is generating the assets. The preview UI serves images from a temporary storage/CDN during generation, but the export only includes files that actually exist inside the project directory (`/public`). If the images are referenced by URL (or generated at runtime) they render in preview but won’t be packaged in the downloaded archive. Open the page source in preview and check the image `src`. If it points to a remote URL (vercel blob / temporary storage) instead of `/public/...`, the exporter won’t include it. Try manually downloading one of the images and placing it inside `/public/images` and update the path — you’ll see it appear in the archive.