Roblox Rolls Out Asset Versioning for Meshes, Images, Audio, and Video Starting January 2027

What Changed

Roblox is rolling out asset versioning across four core asset types — Meshes, Images, Audio, and Video — in a phased schedule that starts January 19, 2027. The change lets creators publish updated versions of an asset while keeping the same asset ID, eliminating the current workflow of uploading a brand-new asset, getting a new ID, and manually updating every reference in properties and scripts.

The announcement, posted by Roblox staff member bballerblox on the Developer Forum, frames this as the first step toward making "every asset on Roblox version the same way." Animations already support versioning; they gain explicit version pinning in December 2026.

Rollout Timeline

The rollout is staggered across six dates:

• November 11, 2026 — AssetService:GetLatestVersionUriAsync() becomes available. This API returns an asset URI pinned to the latest version for scripts that always want the newest iteration.
• December 2026 — Animations can be pinned to and loaded at an exact version.
• January 19, 2027 — Mesh and Image versioning goes live. Asset IDs without an explicit version parameter will load a "frozen" version instead of the latest.
• February 17, 2027 — Audio and Video versioning goes live with the same frozen-version behavior.
• February 2027 — Studio workflow for auto-updating asset references to newer versions while editing. References get pinned on place save so published games don't change mid-edit.
• March 31, 2027 — Animation asset IDs without a version load the frozen version.

Roblox notes these are "earliest possible current target dates" and could shift.

How Versioning Works

Creators will publish new versions of an existing asset rather than uploading a duplicate. The asset ID remains constant. To reference a specific version, append &version=N to the asset URI: rbxassetid://1234&version=3. This works in properties, scripts, place files, and Models.

The frozen-version rule is the biggest behavioral change. Today, rbxassetid://1234 always loads the latest version. After each type's launch date:

• Assets created before the launch date load at the latest version that existed on the launch date.
• Assets created after the launch date load at version 1.

This prevents games from unexpectedly changing when underlying assets are updated. Scripts that need the latest version must use the new GetLatestVersionUriAsync() API or explicitly pin a version number.

Impact on Plugin and Tool Developers

Roblox is explicitly calling out plugin creators: update your tools before January 19, 2027. Once versioning goes live, pinned URIs like rbxassetid://1234&version=3 will appear in creators' assets and games. Plugins that parse asset IDs from URI strings can break — for example, a pattern like :match("%d+$") would return 3 (the version) instead of 1234 (the asset ID).

Other common issues flagged:

• Constructing content strings without a version number (e.g., "rbxassetid://" .. AssetId) locks the asset at its frozen version.
• Numeric asset ID comparisons (assetId1 == assetId2) no longer guarantee the rendered content is identical; compare full URIs instead.

Roblox has published test assets with multiple versions so developers can validate their plugins now:

• Mesh: 95550017627403
• Image: 94950710471595
• Audio: 82118835858107

What Stays the Same

Models, Packages, and Avatar items keep their current loading behavior. However, Meshes, Images, Audio, Video, and Animations referenced inside them follow the new versioning rules. InsertService:LoadAsset() and AssetService:LoadAssetAsync() continue to load the latest version regardless of the frozen-version change.

Why It Matters

For everyday creators, versioning means less inventory clutter and fewer broken references when iterating on art and sound. For tooling authors, it's a breaking change in how asset identifiers work — one that requires code updates before the January deadline. The frozen-version default is a stability guarantee for live games, but it shifts the burden onto scripts that do want the latest version to be explicit about it.

Roblox says it will update the announcement post if dates shift. The next milestone is the API launch on November 11, giving plugin developers roughly two months to adapt before the first asset types go live.