Redesigned Place Version History in Studio

[LuckyRainGG]

Key Takeaways

In the coming weeks, we’re rolling out a revamped Place Version History that lets collaborators tag, search, filter, and manage place versions all in a flexible new interface.

[Update] March 6, 2026

@LuckyRainGG

Hey Creators,

Thank you for all your support and thoughtful feedback!

Based on your early feedback, we made a quick adjustment:

Publish notes will be optional

When you publish, you won’t see a dialog to add notes. Instead, you’ll see a simple confirmation toast with an optional “Add notes” button. It’s completely optional and there if you want to capture notes. We wanted to make this available to you right away so our team fast-tracked this change and it will be part of the release.

We’re excited about your feedback and will continue to evolve Place Version History in partnership with you. Thank you for being on this journey with us. More to come!

Hey Creators,

Get ready for an upgrade to how you manage and track changes in your projects! We’re excited to introduce a completely redesigned and feature-rich Place Version History in Roblox Studio.

Introducing a Revamped Place Version History

We know how much versioning matters as projects and teams increase in size. That’s why we’re building new workflows to make version management in Studio seamless starting with a complete revamp of Place Version History.

The new Place Version History enables collaborators to tag, search, filter, and manage place versions using metadata such as timestamps, usernames, and notes all in a flexible new interface. Whether it’s for a rollback, development milestone, or stable release, this tool is designed to help you quickly find the right checkpoint every time.

Powerful New Product Features

We’ve rebuilt Place Version History from the ground up to be more visible, actionable, and informative.

Version Notes: Add descriptive notes to your saved and published places to create clear checkpoints for development milestones.

Powerful Searching: Search across Version Notes to instantly find the version you’re looking for.

Advanced Filtering: Filter by Date Range, Save Type (auto vs. manual), Published Saves, Collaborator, and whether a save has notes.

Track Collaborators: Easily see who was in a place edit session and who performed the save.

Dockable Widget: Place Version History is now a dockable widget. You can position it anywhere in your Studio layout, allowing you to work side-by-side within the context of your project.

Easy to Access & Review

Get Started Instantly: The new place version history is just a few clicks away. Here’s how you can access it:

• System Menu > Window > Version History
• Asset Manager > Places > Right-click > View History

New Saving Shortcut: We’re helping versioning easily fit into your workflow with a new saving shortcut:

• Save with Notes: Use Cmd + Option + S (Mac) or Ctrl + Alt + S (Windows) to save the current place version with additional version notes.

Edit Past Version Notes Anytime: You can go back to any previous version and update it with a name and description, making it easier to organize and search through old history.

What to Look Out For

Legacy Version Limitations: Versions created before this feature existed cannot be searched or filtered using the new metadata (e.g. Auto-save vs. Manual-save). However, you can add notes to older saves to make them searchable.

Publishing vs. Saving Requirements: We’ve made version notes required when you publish to help you keep track of what went live to your players.

This feature will be rolling out in the coming weeks! We encourage you to try it out and let us know what you think. We would love to hear your feedback on what would be most useful to continue improving Place Version History.

Happy creating!

Many thanks to the wonderful team: @vreddym, @code4xp, @wingedbreadsticks, @VV_Wesco, @PixelPlumber, @MoodyMandyMeow, @Rusi_002, @verybarkypuppy, @DevOdysseus, @akssoggywall

[ChiefWildin]

@LuckyRainGG

Publishing vs. Saving Requirements: We’ve made version notes required when you publish to help you keep track of what went live to your players.

This is great, except for this one little part. I want to be able to publish as fast as possible. Especially if I’m fixing a critical bug introduced with an update (although let’s be real, that’s never happened before, right guys?), and time is of the essence. I don’t want to be slowed down by being forced to type some garbage in the notes. Let me do that afterwards instead, once the dust settles. Enable me with the freedom to choose.

[Zorvep]

I love seeing Roblox making tooling more integrated, great update! However I would like the ability to publish my games without notes.

[RocketSlither (Distinguished_Gent)]

Will we be able to make these patch notes public? Like our game will have a tab called “patch notes” and they can see the versions and patch notes.

Where can players view these patch notes?

[PeZsmistic]

Will this pave the way for on-platform change notes accessible by players?

[weakroblox35]

And could we have edit-only visible private patch notes? Could be used for debugs and such

[nix102on (HyperHunter)]

Thank you. I will try to rollback Roblox to the jurassic days.
Hopefully it will work.
Or we are doomed.

[Entelogical]

Agreed, notes should not be required!

[Real_Daytern (Daytern)]

Since you are using AI in so many parts of Roblox, why not use it where it would really make a difference?

Do you know how cool it would be if AI could analyze your world and summarize everything you modified compared to the previous version?
This way, developers could automatically receive notes without being forced to write them manually every time they publish a new version.

This is the perfect use case for AI right there.

[FishEye18 (SmallAndMischievous)]

[PeZsmistic]

I would like this same behavior for script commit messages too.

Autogenerate draft commit messages

I am lazy and I don’t want to have to type out a mundane commit message every time I commit my drafts. I commit scripts multiple times as I work on the same feature and rarely get the chance to write a high level commit message that encompasses the whole change set, and it’s a serious chronic problem. As a result, my script history is pretty useless in the history list because none of the commits have messages. [image] I want an option in the draft commit popup to allow Roblox to read the edi…

[maxim01689]

This is really awesome, but could we get control over online auto saving? It saves tiny edits every 5 minutes, which is nice, but that’s very wasteful for storage when i don’t usually face issues that requires me to check auto saved so often.

[BenjiThePug14 (pogpug)]

Finallyyy!! I loved going back to different versions and the old one was just so… clunky? I LOVE THIS!

[WinterStorm_Meow (Winter)]

This announcement was so good I had to say something. W update, finally a great update and this is a game changer! I have been doing this when saving to file where I would name milestone updates! Thank you! Now I can automate this.

[CcXxiiHuman_C4t (HumanCat222)]

@LuckyRainGG

Publishing vs. Saving Requirements: We’ve made version notes required when you publish to help you keep track of what went live to your players.

Publishing isn’t always to a large amount of players, I have a testing place and games in private test which I very often publish to because I need to test it in the client or a small fix/change for testers. Having to write a note every time will be annoying. Can this not be a requirement for private places?

[TimeFrenzied (xand)]

Can we get an option to create change logs that users can see on the game page?

Also, how will this work when saving? Will it pop up asking me to add a description or will I have to do it manually? Maybe you can add a keybind to save with description and use said description on the next publish?

[P7_Error]

Could we get the feature for PackageLinks not self update when rolling back place versions or downloading place versions?

[sleitnick]

I’ve wasted so much time randomly switching to old versions to find what I need. This is a very valuable add!

[Blueeple (Bue)]

Now that means that every developer on my team FINALLY doesn’t have to check github for any changes in terms of scripting, and now I can search up game versions instead of scrolling for 2 years