Roblox sets target dates for asset versioning and frozen references
Roblox plans asset versioning with frozen default references. Audit plugins and animation update workflows before the loading rules change.
Roblox has announced asset versioning changes affecting game developers and plugin authors. Its November 5, 2026 announcement targets January 19, 2027 for Meshes and Images, followed by Audio and Video on February 17, 2027. Creators will retain asset IDs across revisions. Roblox says these are the earliest possible target dates and could move later.
References will stop following updates
After each asset type launches, references without a version will load frozen content. For assets created before launch, that means the latest version at launch; assets created afterward default to version 1. Explicitly versioned URIs will select a particular revision. Roblox says existing content will not visibly change on those dates.
Animation pinning is targeted for December 2026. On March 31, 2027, unversioned animation references will freeze, so later animation publications will no longer automatically reach games. Teams relying on automatic updates should switch beforehand to pinned references or AssetService:GetLatestVersionUriAsync(), targeted for November 11, 2026. Roblox says this API returns a URI pinned to the latest revision.
Models, Packages and Avatar items retain their loading behavior, but affected assets referenced inside them follow the new rules. InsertService:LoadAsset() and AssetService:LoadAssetAsync() still retrieve the latest version. Studio’s planned February 2027 workflow will refresh references during editing and pin them when saving places.
Test plugin assumptions now
Our recommendation is to audit URI parsing and content insertion this week, ahead of Roblox’s January 19, 2027 plugin update deadline. Use the announcement’s versioned sample assets to check that tools preserve version information. A parser that extracts trailing digits can mistake a version for an asset ID. Also check comparisons: matching numeric IDs does not establish matching content. We'd start by testing a full import-and-save cycle, verifying that the selected revision survives.