Browser save and performance notes

Why WebGL shows up in game errors

RPG Maker web exports often render through browser graphics APIs. MDN describes WebGL as a browser API for high-performance 2D and 3D graphics that can use hardware graphics acceleration when the device supports it.

That lines up with the Flesh, Blood, & Concrete itch page, which tells players to enable hardware acceleration in Chrome for one startup error and otherwise use a browser with WebGL support.

Why saves can break in a browser frame

Browser save behavior is not the same as a desktop save folder. MDN explains that web storage is partitioned by origin, and third-party iframe access can be affected when third-party cookies are disabled.

Flesh, Blood, & Concrete makes the practical version of that warning explicit: the official page says cookies are required for save and options data in the browser build. If saving matters, stay in the same browser profile and avoid private windows.

Video and input compatibility

Some RPG Maker builds use video files for cutscenes or interface moments. MDN lists WebM as a web video container used with modern codecs, while the Flesh, Blood, & Concrete page specifically warns that browser .webm support affects playback.

Input support is just as important. Mistrick can load in a browser, but the official page says the main browser version is keyboard-only. A mobile port exists, but it uses a virtual keyboard, so touch play should be treated as a special case.

• Use a current desktop browser for the most predictable experience.
• Keep cookies/storage available if you care about in-browser saves.
• If a browser build keeps failing, check the official download link for an offline build.