Roblox 739 Update, 2026-09-17: What's New
Contents
The Roblox 739 update is mainly about Luau speed and Studio workflow, not new player-facing features. The “Release Notes for 739” were published in the official documentation on 2026-09-17 and split into two sections: Improvements and Fixes.
Here’s what actually made it in, the conditions under which these changes won’t reach you, and what Roblox left unsaid about this release.
What’s in 739
The most visible part is the scripting engine. Dynamic-key table access (when the key is computed at runtime rather than written in code) got cheaper on both sides:
| Operation | How much faster |
|---|---|
| Dynamic-key read | 10-18% |
| Dynamic-key write | 18-25% |
Table resizing on key insertion was sped up separately. There’s also a behaviour change that’s easy to miss: inserting a non-numeric key no longer forces a pre-allocated array portion of the table to shrink. In practice, that’s the case where you build a table with a size set in advance, then add a named field to it — previously, doing that ate into the benefit of the earlier pre-allocation.
Metamethods got cheaper too. Call dispatch cost is down 5-25%, and for metatables frozen via table.freeze, the overhead of the metamethod lookup itself is cut separately and by a larger margin. If you’ve ever wondered why freezing tables is recommended as an optimisation trick, that’s another reason for it — the language basics are covered in the guide on Luau.
Next, Studio. Cursor jitter during dragging is fixed, and camera pan speed can now be configured in Studio Settings. Fluid force visualisation in mechanisms gained three new components: air lift, water lift, and water drag. Cameras you insert by copying or importing an rbxm are now automatically promoted by Studio to ViewportCameras with the same properties preserved, so ThumbnailCameras and ViewportFrames don’t get mixed up during authoring. A Luau autocomplete bug that stopped suggestions from appearing in various scopes of the program is also fixed. If you’re just starting out, there’s a separate guide on your first game in Roblox Studio.
The rest touches experiences themselves:
- TV remotes. A new rollout-state property,
MapTVRemoteToGamepadKeycodes, was added under Workspace — it controls whether an experience automatically maps TV remote keycodes to legacy gamepad keycodes. On by default. - In-experience publishing. In-experience publishing via Opaque Content is enabled.
- Animation. An
AnimationNodeType.OneShotNodenode type was added to the animation graph. - Chat.
ChatWindowConfiguration.TextChannelDisplayModelets a creator choose whether the main chat window shows all TextChannels (as before) or only channels created throughTextChatService.CreateDefaultTextChannels. - Tools. Fixed a case where tools failed to stream to some clients.
- Empty WorldModels. Simulation performance with empty WorldModels improved.
- glTF export. If a part is omitted because its mesh produced no geometry, a warning with the mesh’s content ID is now written to the log, so the omission can be matched to a failed asset load. Previously the part just vanished — no node, no mesh, no log line — while the export still reported success. The exported file itself hasn’t changed; only the logging output was added.
Under what conditions these changes won’t reach you
The label next to each item matters as much as the item itself.
Most entries in 739 carry a Pending status. Roblox marked it directly in the notes and didn’t explain it further. “It’s on the list” and “it’s already live on your client” aren’t the same claim.
glTF logging is off by default. It’s gated by the FFlagGltfExportLogOmittedInstances flag. While the flag stays off, export behaviour doesn’t change for you — and you still won’t see a vanished part in the log.
MapTVRemoteToGamepadKeycodes is a rollout-state property. Its purpose is to enable automatic mapping; since it’s active by default, experiences that handle remote input themselves are exactly the ones worth checking. More on what else affects input handling is in the guide on controls and accessibility.
The chat change is an option, not a new default. TextChannelDisplayMode lets you describe the behaviour you want; the notes name the “all TextChannels” behaviour explicitly as the previous one.
The Luau speed gains are tied to specific operations. The percentages given apply to dynamic-key reads and writes and to metamethod calls. Code that doesn’t hit those paths isn’t mentioned in the notes at all — don’t build expectations about your experience’s overall frame rate on these numbers. General profiling approaches are covered in the guide on performance optimisation.
What’s not known about 739
The list is shorter than the release itself, but it’s an honest one.
- What Pending means for timing. No rollout dates, stages, or exit conditions for that status appear in the notes.
- When the glTF flag will be switched on. Roblox only says it’s off by default. Nothing is said about plans to enable it.
- Which scenarios see the largest Luau gains, and which see the smallest. Ranges are given for the operations, not the measurement conditions, hardware, or test code.
- The cause of the tool-streaming issue. It’s noted as fixed; who exactly it affected and under what circumstances is not.
- What happens to Cameras that are already placed. The notes describe promotion to ViewportCameras specifically on insertion, whether by copying or importing an rbxm.
- Whether any of this affects cost or terms for creators. There’s no mention of this in 739 at all.
Every one of these points has the same nature: Roblox didn’t comment on it, rather than “hasn’t announced it yet.” We won’t fill in the gaps on its behalf — earlier releases are collected in the updates and release notes overview.
In short
Release 739 from 2026-09-17 is a technical one: faster Luau tables and metamethods, small Studio conveniences, a few fixes. Most items are marked Pending, and logging of omitted glTF parts is off by default, so you may simply not see some of these changes.
Frequently asked questions
What's the headline change in the Roblox 739 update?
Most of it is Luau performance: faster dynamic-key table access and cheaper metamethod calls. The rest covers Studio and a handful of fixes.
When did update 739 release?
The "Release Notes for 739" were published on 2026-09-17 in the official developer documentation.
Does anything here change for me as a player?
The notes name few player-facing items directly: a fix for tools not streaming to some clients, and automatic mapping of TV remote keycodes to legacy gamepad keycodes, on by default.
What does the Pending label in the notes mean?
It's a status Roblox attached to the entries itself. Most items in the 739 notes carry it, and there's no further explanation or timeline attached.
How much faster did Luau tables get?
Dynamic-key access is listed as 10-18% faster for reads and 18-25% faster for writes. Metamethod call overhead is down 5-25%.
Do I need to switch anything on manually?
Logging of omitted parts during glTF export sits behind the flag FFlagGltfExportLogOmittedInstances and is off by default. Nothing else in the notes calls for a separate toggle.