Upcoming builds

Windows · macOS · Android · home

An upcoming build is a Roblox build that exists and can be seen, but that production is not serving yet. On Windows and macOS it has been published to Roblox's pre-release channel; on Android it has been staged on the mirror before Google Play finishes its rollout. It usually becomes the live build within about a day.

Every platform page shows it in the Upcoming row, between Status and Previous, and every endpoint below reports it.

Why it is worth watching

On the release this was built around — Windows 0.738.0.7381397 — the timeline was:

UTC, 2026-09-09	What happened
17:07	The client package appeared on Roblox's CDN. From here it can be downloaded and dumped.
17:54	A default offsets set existed upstream.
22:30	Production switched to it.

More than five hours in which the build exists, can be fetched from this server, and can have verified offsets published for it — before most players have it.

Where it comes from

Roblox's own channel API, which Windows trackers traditionally used for this, answers 401 Unauthorized for every channel except LIVE to an anonymous caller. So this server reads the places that still answer:

Source	Gives	Used for
WEAO's future endpoint	Hash and dotted version, Windows and macOS	Detection
theo's build listing	Hash of every build with a dump, Windows	Confirmation, and detection when WEAO is down
Roblox's per-channel deploy logs	Dotted version and time only — Roblox redacts the hash	Early signals, never a build
An authorised ZBeta origin	Hash and dotted version	Detection, when the operator configures one
Roblox's CDN	When the package was actually published	The deploy time
The Android mirror	Staged APKs	Android

The deploy time comes from the CDN's own Last-Modified, not from any tracker's timestamp. Roblox's deploy logs are written in US Pacific time, and at least one widely used source reads them as Eastern — three hours out.

GET /api/v1/{platform}/upcoming

curl -s https://rbxoffsets.com/api/v1/windows/upcoming

{
  "platform": "windows",
  "upcoming": {
    "version": "version-0123456789abcdef",
    "displayVersion": "0.739.0.7390681",
    "upcomingAt": "2026-09-12T17:09:40.000Z",
    "deployedAt": "2026-09-12T17:07:13.000Z",
    "sources": ["weao", "imtheo"],
    "cdnAvailable": true,
    "stored": true,
    "download": "https://rbxoffsets.com/download/windows/version-0123456789abcdef",
    "offsets": { "tiers": ["default"], "bestTier": "default", "url": "https://rbxoffsets.com/api/v1/windows/offsets/version-0123456789abcdef" },
    "live": { "version": "version-c5aecda2245e4fae", "displayVersion": "0.738.0.7381397" },
    "page": "https://rbxoffsets.com/archive/windows/version-0123456789abcdef"
  },
  "signals": [
    { "channel": "zcanary", "binary": "WindowsPlayer", "displayVersion": "0.740.0.7400050", "deployedAt": "2026-09-12T15:02:11.000Z", "ahead": true, "hash": null }
  ],
  "sourceHealth": { "weaoFuture": { "ok": true, "checkedAt": "…", "error": null }, "deployHistory": { "ok": true, "checkedAt": "…", "error": null } },
  "checkedAt": "2026-09-12T17:10:00.000Z"
}

Field	Meaning
`upcoming`	`null` when nothing is ahead of production. That is the normal state for most of any week.
`upcomingAt`	When this server first saw it ahead of production.
`deployedAt`	When Roblox published it to its CDN. `null` until the package exists there.
`cdnAvailable`	Whether the package can be downloaded from Roblox right now.
`stored`	Whether this server holds a copy, so `/download/` works for it.
`offsets.tiers`	Which offsets tiers exist for it yet. See Offset tiers.
`signals`	The newest deploy-log sighting per Roblox channel. `ahead` marks ones newer than production. There is no hash, so nothing can be downloaded from a signal.
`sourceHealth`	Whether each source answered on its last check. A failed source with `upcoming: null` means "could not tell", not "nothing is upcoming".

The other forms

curl -s  https://rbxoffsets.com/api/v1/upcoming               # every platform at once
curl -s  https://rbxoffsets.com/api/v1/windows/upcoming.txt   # the hash as plain text; 204 when there is none
curl -s  https://rbxoffsets.com/api/v1/windows/channels       # live, upcoming, previous and every channel sighting
curl -s  https://rbxoffsets.com/api/v1/windows/builds/version-0123456789abcdef # the build's whole record

What an upcoming build does not promise

It may never ship. Roblox pulls pre-release builds. When a different build replaces it before it goes live, this server records upcoming_withdrawn and the build's lifecycle stays future or becomes passed_over.
Production can go backwards. A revert moves production to an older build, and upcoming detection starts again from there.
It is not the same as "newer". A build flagged by hand by an operator is marked with source manual; treat it with the trust you have in that operator.

Acting on it

# poll every few minutes; act when the hash changes
next=$(curl -fsS https://rbxoffsets.com/api/v1/windows/upcoming.txt)
[ -n "$next" ] && echo "upcoming: $next"

# wait until it has verified offsets, then fetch them — before it goes live
curl -fsSL -o offsets.hpp "https://rbxoffsets.com/api/v1/windows/offsets/$next/hpp?tier=verified"

When it goes live, the live event carries leadSeconds — how long it was visible first — and the Upcoming row clears on the next page load.

Android

Android's upcoming build is the newest build staged on the mirror ahead of production. It has a future lifecycle and, on the Android page, its own section with an ABI verdict per build. There is no deploy time and no signals, because Google Play publishes neither.