Roblox Package Overrides: edit a package in your place while keeping source updates
Posted: Sun Oct 18, 2026 1:04 am
Packages let you reuse content across your places, but customizing one used to mean losing future updates. If you repainted a shared car package, every later update from the author overwrote your paint job. Package Overrides, now in Studio Beta, fixes that. You edit a package in your place, keep your edits, and still receive updates from the source package.
How overrides work
Studio tracks each change you make to a package as an override and reapplies it whenever the source package is updated. When the package author adds new tires or chrome trim, all of your instances get them, and your repainted one keeps its color.
The rules:
Usability improvements
The same update removes friction that used to come with package editing:
If you use Team Create, have everyone in the session enable the beta together. Edits made from a Studio without the beta aren't tracked as overrides, so a package update may not keep them.
Source
[1] Roblox Developer Forum: Package Overrides and Usability Improvements (October 15, 2026)
How overrides work
Studio tracks each change you make to a package as an override and reapplies it whenever the source package is updated. When the package author adds new tires or chrome trim, all of your instances get them, and your repainted one keeps its color.
The rules:
- If you and the source changed the same property, yours wins.
- If an update deletes an instance you changed, Studio drops that override.
- When you publish, your overrides become part of the new version.
- Changes inside a nested package are kept as overrides on the parent. If you later change the nested package's version, they apply again on top of it.
- Update Studio to version 743 or later.
- Go to File > Beta Features.
- Enable Package Overrides.
- Restart Studio.
Usability improvements
The same update removes friction that used to come with package editing:
- No warning dialogs. Editing or reverting a package no longer stops you with the Modified Packages dialog.
- Auto Update on edited packages. A package you edited couldn't use Auto-Update. You can now keep it on after you edit.
- Status at a glance. The icon and tooltips now say whether a package is on the latest version, pinned, or pinned with updates available. A blue dot means it has overrides.
- Publish parents with modified children. Publishing a parent package that contained modified child packages wasn't possible. It is now.
- Full version history. Studio used to list only the latest 50 versions, and notes on older versions disappeared. Version history now shows every version with its notes.
If you use Team Create, have everyone in the session enable the beta together. Edits made from a Studio without the beta aren't tracked as overrides, so a package update may not keep them.
Source
[1] Roblox Developer Forum: Package Overrides and Usability Improvements (October 15, 2026)