Upload and use project assets

Supported files and limits

Project Assets supports PNG, JPEG, GIF, WebP, ICO, WOFF, WOFF2, MP3 and MP4. Each file can be up to 10 MB. Assets count against the same organization storage allowance used by deployment artifacts and storage reservations; there is no separate project-asset quota. The Free plan currently includes 100 MB of shared storage. Check the published pricing catalog for the current allowance on every plan.

Active source files such as HTML, JavaScript and SVG are not accepted as Project Assets. Keep text source in the editor where it can be reviewed and versioned.

Upload from the Explorer

1. Save the current workspace.
2. Select a frontend folder, then use Upload asset, or drag a supported file into that folder.
3. Wait through upload, security scan and content validation until the asset is marked ready.
4. Import or reference the file using its path in the project tree.

Project Assets belong in the frontend workspace, not inside a backend module source root. Uploading another file with the same name can replace the existing asset after validation. A workspace revision conflict asks you to save or reload before trying again so concurrent edits are not overwritten.

Security and integrity

BlinkHost uploads each file through a short-lived, write-only capability into private quarantine storage. The file must pass malware scanning, checksum verification, media-signature and structural validation before it becomes available. Image dimensions and supported video structure and duration are bounded. If scanning is unavailable or incomplete, the upload fails closed and production is unchanged.

Asset storage is private. The IDE receives short-lived read access only for an authorised project and verifies the file checksum before mounting it in the WebContainer workspace.

Remove an asset

Delete the asset from the Explorer and save the workspace. BlinkHost removes the project reference and schedules unreferenced stored data for cleanup. If the same content is still referenced safely elsewhere in the project, storage cleanup preserves the live reference.

If an upload is rejected, read the visible reason before retrying. Do not rename executable content to a supported extension; file contents must match the selected media type.