Roblox Low-End Streaming Changes (October 2026): Adaptive Radius, Path Pre-fetching, 500 Studs, and SLIM

Thu Oct 22, 2026 1:39 pm

Quick Summary

Roblox is changing how much of the world a weak device has to handle. Three items from the Fall 2026 Creator Roadmap land in this window: adaptive streaming radius, path pre-fetching, and a minimum draw distance of 500 studs, up from 200 today.
Two of those are engine-side and invisible. Adaptive radius and path pre-fetching are engine behaviour. Nothing in your place file controls them, and neither one is listed as an opt-in setting yet.
The 500 stud change is different. It raises a floor that sits at the bottom of the quality ladder, so every experience gets more view distance at quality level 1, whether the developer asks for it or not.
Streamed-out content is already not drawn. Draw distance only decides how much detail is visible, so on an open map the two changes multiply. That is why SLIM stand-ins and the adaptive radius both exist.
Expect a retest, not a surprise. Roblox has not published a performance cost for the new floor, and neither has anyone else.

What actually changed for low-end hardware

The items worth knowing about are all on the engine side of the fence, which is a polite way of saying you cannot turn them off from Studio.

Adaptive radius (Late 2026): the engine adjusts each player's streaming radius based on that device's memory and CPU. Right now the streaming radius is set per place, not per player.
Path pre-fetching (Late 2026): the engine predicts player movement and streams content along likely routes, with the stated goal of preventing pop-ins and gameplay pauses.
Minimum draw distance 500 studs (Late 2026): the minimum draw distance on low-end devices goes from 200 to 500 studs. Roblox's own RDC summary says this applies to a low-end Android device running at quality level 1, and that it is more than double today's 200.
SLIM for NPC characters and for rigid welded items (Early 2027): both are listed on the roadmap but not yet live, so do not build around them.
Improved collision pipeline (Late 2027): listed as significantly improving collision performance for CPU and memory, and the farthest-out item on this list.

The 500 stud floor has a dependency worth flagging. Frustum streaming streams instances that fall inside the camera view but outside the normal streaming radius, and it turns itself off automatically when a client's draw distance drops to or below the normal streaming target radius. Raising the floor raises the bar frustum streaming has to clear before it activates at all. Nobody has published what that does to memory on a level 1 device, and the roadmap entry does not say.

Draw distance is not the same as streaming

This is the part people get wrong, and it is worth being precise because it decides which change helps you.

Streaming decides what is loaded. The engine replicates instances in a cube around the replication focus, which is the player's character PrimaryPart by default. You can move it with

Code: Select all

Player.ReplicationFocus

or add more with

Code: Select all

Player:AddReplicationFocus()

.

Draw distance decides what is drawn. Lower graphics levels cut how far detail is rendered.

That gap is where the visible problem sits. Under SLIM, a model that has streamed out is not invisible. The engine keeps a lightweight composite stand-in in the DataModel and renders that instead, so a building you walked away from still shows up in the distance as a cheap version of itself. The composite is a real triangle cost, but it is small compared to the full model, and Roblox's own SLIM page carries the numbers: an audience at far distance goes from roughly 2,600,000 triangles and about 60,000 client instances without SLIM to about 170,000 triangles and 4,000 client instances with it. Near proximity goes from about 670,000 triangles to about 100,000.

So on a level 1 phone in an open world, you get more of those stand-ins drawn at once after the floor goes to 500 studs. That is the real cost question, and it is the one nobody has answered yet.

Recommended streaming settings right now

These are the values the official techniques guide lists as recommended. All of them are non-scriptable, so you set them on the Workspace object in Studio, not from a script.

EnableSLIMAvatars: Enabled, to render R15 avatars as lightweight animated stand-ins when appropriate.
ModelStreamingBehavior: Improved, the most efficient streaming for models with BasePart descendants.
StreamingIntegrityMode: PauseOutsideLoadedArea, which pauses a player who walks into an area that has not streamed in yet.
StreamingMinRadius: keep the default of 64. The docs are blunt about this one: raising it costs memory and server bandwidth.
StreamingTargetRadius: keep the default of 1024. This is also the farthest distance at which players see full detail.
StreamOutBehavior: Opportunistic, so the client garbage collects content aggressively and avoids out-of-memory crashes.

Two rules follow from the same page. StreamingTargetRadius must be larger than StreamingMinRadius, because the band between them is a buffer for when the client stops receiving content. If you set them equal, you get network pauses. And keep each model's spatial extent under roughly 64 cubic studs, because that raises the chance the whole model streams in as one unit.

What to test, in order

Set StreamingTargetRadius to its minimum of 64 and play. Some streaming bugs only show up when the streamed area is small.
Teleport between distant areas, then walk back. Stream in and stream out get exercised hardest during transitions, not near spawn.
Open the streaming debug overlay. In a live experience press Shift+F3, then Shift+1 repeatedly until the fourth panel appears. In Studio playtests it is Shift+Ctrl+F3 on Windows.
Watch the Output window and Developer Console. Many streaming bugs throw errors instead of misbehaving quietly, and the ones that matter usually read
Code: Select all
```
attempt to index nil with ...
```
.
Test with SLIM on and off. If the frame rate gap is small, you are not memory bound and the new draw distance floor will not bite you.
Check the frame budget. Roblox games target 60 FPS by default, which is 16.67 milliseconds per frame. Anything you cannot fit in that budget is a problem regardless of settings.

Script patterns that break under streaming

Direct indexing

Code: Select all

local door = workspace.House1.Door

throws if House1 or Door has not streamed in.

Code: Select all

FindFirstChild()

,

Code: Select all

FindFirstChildWhichIsA()

and

Code: Select all

FindFirstChildOfClass()

return nil instead. Wait with

Code: Select all

WaitForChild()

if the script cannot continue without the instance, or nil-check and skip the work for that client.

Stale properties

Once an instance streams out, property updates stop replicating. Reading

Code: Select all

BasePart.Position

still works, it just returns the last replicated value, which can be arbitrarily old. Move distance checks to the server, where scripts see every instance all the time.

Loading screens that hang

A map cloned from ReplicatedStorage into Workspace and waited on by the client can hang forever under streaming, because the character has not spawned yet, so there is no replication focus, so the map never streams in. Signal readiness once the character exists and the immediate area is loaded, or call

Code: Select all

AddReplicationFocus()

at the spawn point before the character appears.

Signals that fire on stream in

Code: Select all

ChildAdded

,

Code: Select all

ChildRemoved

and the CollectionService signals all fire when content streams in and out, and a receiving script cannot tell the difference from the signal alone. If you play a spawn effect when an enemy appears, tag the enemy with an attribute on first spawn and skip the effect on later stream-ins.

Local clones

Reparenting an instance locally from ReplicatedStorage into Workspace makes it eligible to stream out. Cloning one locally creates a client-only copy that stops receiving updates from the server-owned original. Calling

Code: Select all

Destroy()

on the client for a server-owned object removes it locally and it streams straight back in with its original state.

FAQ

Will my low-end players get better graphics for free?
More of the map, in most open-world cases. The floor goes from 200 to 500 studs, and Roblox says that is more than double. Roblox has not published what it costs in performance, so treat it as an unmeasured gain and recheck your settings when it ships.

Can I opt out of the 500 stud minimum?
Nothing published suggests you can. It is described as a change to the minimum draw distance on low-end devices, not as a place setting, and it is not on the list of properties you control in Studio.

Does raising draw distance hurt memory?
It can. Draw distance decides how much detail is rendered, and every stand-in the engine keeps in the DataModel is a rendering cost. The SLIM avatar numbers are the only published figures here, and they show what enabling the lightweight path saves rather than what the new floor costs.

What is SLIM again?
Scalable Lightweight Interactive Models. It generates optimized composite meshes and multiple levels of detail in the cloud, then renders the cheap version when the full model is streamed out or when the composite is simply more efficient. It requires StreamingEnabled, a place saved to Roblox rather than a local .rbxl file, and Team Create enabled.

Do SLIM avatars work for any rig?
No. R15 avatars with a body, dynamic head, and a standard or advanced R15 rig are supported, with rigid and layered accessories. R6 avatars, NPCs, and avatars with custom proportions or body scaling are excluded.

Why does my game look different on my friend's phone?
Since Unified Lighting went fully live on July 23, 2025, each experience chooses whether to protect lighting or draw distance when quality drops. Two experiences at the same quality level can look and run very differently, and that is a design choice, not a bug.

Sources