What's new in Roblox update 734

18 August 2026 · 5 min read

GameMapa editorial · how we check facts
Checked: Claude (AI) — fact-checked against the Ukrainian original; not proofread by a native speaker

Roblox update 734 came out on 2026-08-11 and consists mostly of changes for developers working in Roblox Studio: a new ViewportCamera type, collision group APIs moving to WorldRoot, a new Collections beta, and a set of fixes in Luau and the animation system — the notes don’t list any direct new content for players.

Below is a walkthrough of exactly what the developer’s official notes say, what they don’t say, and how to verify the facts yourself.

What shipped in 734

The “Release Notes for 734” were published on 2026-08-11 through Roblox’s official developer channel. The update number is stated directly in the title — 734.

The notes are split into two sections: Improvements and Fixes. That’s the standard structure the developer uses for these posts, not a list of separate in-game systems — the section names are kept in English in the notes themselves.

Camera and physics

The main change without a [Pending] tag is a new Instance type called ViewportCamera. It inherits from the Camera class, but unlike a regular camera it replicates — meaning its state is correctly passed along wherever that’s needed. According to the notes, this removes an issue with using ThumbnailCameras in Team Create and with ViewportFrame objects set up at design time.

The second change in this block moves the collision group APIs from PhysicsService to WorldRoot. As a result, each WorldModel will be able to register and configure its own collision groups independently of Workspace. A new property, UseWorkspaceCollisionGroups, is being added: turning it on makes a given WorldModel use Workspace’s collision groups instead of its own.

Developer tooling

There are two items about working tools. First, the Collections API gets a new entry point — the notes don’t give any detail on what specifically changes about using that API. Second, Roblox Studio is getting a new Studio Beta called Collections.

Audio

Classes and services with the AcousticSimulationEnabled property turned on — SoundService, for example — are getting subcategories. Occlusion (sound muffling caused by obstacles) and Reverb can now be turned on or off independently of each other, rather than only together.

Interface and images

Several items sit here. TextBox objects with the TextEditable property set to false can now have their text, TextBox.Text, copied on mobile devices without the on-screen keyboard appearing.

Among the EditableImage functions, a new one called SampleImageProjected is being added — it works in the opposite direction to the existing DrawImageProjected: the projection defines how to sample texels from the source texture and place them onto the decal texture. Alongside it comes another blending mode, ImageCombineType.Subtract, which subtracts the source image’s colour and alpha from the destination image.

UIShadow is getting two new properties. UIShadow.Inset lets a shadow render above and within the parent element, not just outside it. UIShadow.ShowBehindParent controls whether the part of the shadow hidden behind the parent element is shown.

Luau and animation

In Luau, the wording of type mismatch error diagnostics has been updated — the developer describes the messages as more succinct and easier to understand. In the New Luau Type Solver, a bug was fixed where inferring an indexer on a table used to return unknown instead of the actual indexer type; that’s now corrected. Another item allows pcall and xpcall to be used inside Luau’s user-defined type functions.

In the animation system, the AnimationId field on a ClipNode (one of the AnimationNodeType entries) can now be connected to a parameter and set at runtime via AnimationTrack:SetParameter. Separately, the parameter count limit for an animation graph has changed: exceeding the limit used to stop the graph from playing outright, and now it’s a soft limit — the graph keeps running, with only a warning about incompatibility with Server Authority.

What the notes don’t cover

To avoid reading in anything extra, here’s what 734 does NOT include according to the developer’s text:

• no new game modes, maps, or events for players;
• no changes to the economy, pricing, or Robux;
• no list of specific games this update affects;
• no explanation of what the [Pending] tag technically means for most items;
• no date for the next update.

If you see a claim about any of these attributed to “update 734” elsewhere, it isn’t based on the official notes covered here.

How to check it yourself

1. Open the developer’s official notes at create.roblox.com/docs/release-notes/release-notes-734.
2. Compare the Improvements and Fixes sections against the summary above.
3. For the primary source, check the developer community forum at devforum.roblox.com and find the topic with the notes for update 734.

Almost every item in update 734 concerns working in Roblox Studio, so if you’re just starting out making games, begin with your first steps in Roblox Studio. The TextBox change on mobile devices matters if you’re testing your game on a phone or tablet — there’s a separate guide on which devices Roblox runs on. And if you’re curious how textures and decals get used outside Studio, say for a character’s look, see the guide on Roblox avatar customisation.

In short

Roblox update 734 (2026-08-11) is a set of changes for developers: a new ViewportCamera type, collision groups moving to WorldRoot, a Collections beta in Roblox Studio, EditableImage and UIShadow changes, and several Luau and animation fixes. The developer’s notes don’t mention any new game modes, maps, or items for players.