Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi! No need to apologize at all, I love seeing people push the engine to its limits!

The 20MB limit is actually a safety guardrail. Since Capsule compiles everything into a single, standalone HTML file, embedding a 181MB video directly inside the file (as Base64 data) would severely hurt the game's performance, cause massive loading times, and potentially crash web browsers due to memory overloads.

How to bypass it for heavy animated backgrounds: Instead of uploading the video directly into the engine's internal storage, you can use an external path!

  1. Place your heavy video file (e.g., my_epic_bg.mp4) in the same folder where you export your game.
  2. In Capsule, instead of importing the file, simply type the local relative path (like ./my_epic_bg.mp4) or a direct web URL in the background field.

This keeps your standalone HTML file ultra-light and fast, while allowing the browser to stream your 181MB animated background flawlessly in the background! Let me know if that works for your interactive setup!

(BTW 181MB is really huge, even a webp could be lighter, so i plan to also add hotspots on videos, it could also help)