Scene JSON Backup Texture Embedding Changes in BabylonJS 5.0

Question

The goal is to guarantee that a BabylonJS scene backup can be restored later without missing textures, even when the original texture files are not available.

Starting with version 5.0, SceneSerializer.Serialize omits base64‑encoded texture data by default, storing only texture URLs unless serializeTextures:true is explicitly set. Consequently, a backup created with the default settings depends on the accessibility of those URLs at load time, and loading multiple backups without disposing the previous scene may retain textures in GPU memory.

Should developers always enable serializeTextures:true for archival backups? How does the default change affect compatibility when upgrading projects from versions prior to 5.0? What is the recommended approach for disposing textures when loading successive backups to prevent GPU memory accumulation?

Tasadduq Burney · Answer

Direct answer
Yes – for archival backups you should call SceneSerializer.Serialize(scene, {serializeTextures:true}).
Why the default changed (confirmed fact)
Starting with BabylonJS 5.0, SceneSerializer.Serialize omits base64‑encoded texture data unless serializeTextures:true is explicitly passed. The serialized JSON therefore contains only texture URLs.
Steps for creating a restorable backup

Ensure you have a reference to the scene you want to back up.
Call const json = BABYLON.SceneSerializer.Serialize(scene, {serializeTextures:true});
Store the resulting string (e.g., save to a file or database).
When you need to restore, use BABYLON.SceneLoader.Parse(json, '', engine); – the textures are embedded as base64 and load even if the original files are missing.

Impact on projects upgraded from pre‑5.0
Projects that relied on the previous self‑contained backup format will now produce URL‑only JSON unless the option is added. To keep the old behaviour, simply add {serializeTextures:true} to every serialization call after upgrading.
Preventing GPU memory accumulation when loading successive backups

Before loading a new backup, dispose the current scene: scene.dispose();
Alternatively, after you are done with a texture, call texture.dispose(); on each texture you no longer need.
Disposing the scene releases all associated textures, geometries, and shaders, returning GPU memory to baseline.

Scene JSON Backup Texture Embedding Changes in BabylonJS 5.0

1 answer

Direct answer

Why the default changed (confirmed fact)

Steps for creating a restorable backup

Impact on projects upgraded from pre‑5.0

Preventing GPU memory accumulation when loading successive backups

Your perspective belongs here.

0 question comments