Manifest V3 · local only · no account

Every Roblox account.
One device.

Only one Roblox session can be live at a time. MultiRoblox keeps all of yours stored on your own device and swaps the live one on demand, so switching stops being a logout, a password and a two-step code.

Download · 27 KB Try the switch

Version: 1.0.0
Accounts: unlimited
Permissions: cookies, storage, tabs
Storage: this device only
Network calls: roblox.com only
Telemetry: none

A Chrome window on the live roblox.com with the MultiRoblox popup open from the toolbar, listing six saved accounts

Aboveone screenshot, nothing composited: a real Chrome window on the live roblox.com, with the real popup open from the toolbar.

1click per switch

0bytes sent off device

27 KBinstalled size

9files you can read

01/ 06 How it works

The session cookie is the account.

Store it, write it back when asked, and the twenty-second ritual disappears. Everything else in the extension exists to make that safe and quick.

01 — Capture

Read the live session

You log in to roblox.com the normal way once. Add current reads the .ROBLOSECURITY cookie, asks the Roblox API who it belongs to, and stores the pair.

02 — Store

Keep it on this device

Accounts live in chrome.storage.local, a file that never leaves this device. The source contains no remote endpoint: the only host it ever talks to is roblox.com.

03 — Restore

Write it back on demand

Clicking a card runs chrome.cookies.set for that account and reloads every open roblox.com tab. The page comes back already signed in.

02/ 06 The difference

Six steps, or one.

Nothing here is a trick. The same session you created by hand is reused instead of being thrown away every time you need the other account.

By handEvery switch

Open roblox.com
Log out of the current account
Type the username
Type the password
Enter the two-step code
Wait for the page to load

With MultiRobloxEvery switch

Click the account you want
The stored cookie is written backAUTOMATIC
Open tabs reload signed inAUTOMATIC

03/ 06 Live example

Click a name. Watch the calls.

The panel on the left is the extension's own interface. The panel on the right is every call it makes when you pick an account, in the order it makes them.

MultiRoblox

Signed in as NebulaForge roblox.com · switched just now

CALL TRACE0 SWITCHES

Click any card on the left. Every line above is a call the extension makes, in order.

The panel on the left is the extension's real interface, styled from the same popup.css that ships in the archive. Each click writes .ROBLOSECURITY for the account you picked and reloads whatever is open on roblox.com. That is the entire mechanism.

04/ 06 Images

The product, screen by screen.

Every frame below was captured from the extension while it was actually running, reading its own storage. Drag the handle on the pair to see the vault fill up.

The vault

first run, and the same popup after six accounts

EMPTYSIX

Nothing is pre-filled and nothing is imported for you. The popup opens empty, says so plainly, and tells you the two ways in.

Press Add current while signed in to roblox.com and the live session is captured with its username, display name, avatar and balance. Or paste a .ROBLOSECURITY value under Add by cookie, which is validated against the Roblox API before anything is stored.

Six accounts later the list is sorted by last use, the live one carries a LIVE marker, and every row is one click away from being the session is actually live.

Screens

Every state, straight from the running build.

05/ 06 Download

Unzip, load unpacked, done.

Three minutes, no store listing, no account. The archive is the complete source: nine small files you can read end to end before you trust them.

MultiRoblox 1.0.0

Manifest V3 · Chromium 102+

ZIP

MultiRoblox.zip

Download the archive

Keep the unzipped folder somewhere permanent. Chrome re-reads it on every launch, so deleting the folder uninstalls the extension.

Requirements

Chromium 102 or newer
Permission to enable Developer mode
About ninety seconds

Contents

MultiRoblox/ ├─ manifest.json ├─ background.js ├─ popup.html · popup.css · popup.js ├─ content.js · content.css ├─ welcome.html ├─ README.txt └─ icons/ 16 · 32 · 48 · 128

Step 01

Open the extensions manager

Type chrome://extensions in the address bar and press Enter. The same page sits behind the three-dot menu under Extensions → Manage extensions.

Step 02

Turn on Developer mode

The switch is in the top right corner. Flipping it reveals three buttons that were not there a moment ago: Load unpacked, Pack extension and Update.

Step 03

Click Load unpacked

Pick the folder that came out of the zip, the one that contains manifest.json — not the zip, and not a folder one level above it. Chrome reads the manifest and the card appears.

Step 04

The card appears

Chrome reads the manifest and lists the extension, with the id it generated for your copy and a link straight to the running service worker. Pin it from the puzzle icon, log in to roblox.com the normal way once, then press Add current. Repeat per account; after that you never type a password again.

chrome://extensions

Developer mode switched on, revealing three new buttons

The Load unpacked button in the Chrome extensions toolbar

The MultiRoblox card on the Chrome extensions page, with its generated id and a link to the service worker

01 / 04

06/ 06 FAQ

The questions worth asking.

Where do my cookies actually go?

Into chrome.storage.local, which is a file in your own profile on your own disk. There is no account, no sync and no server in this project. If you want to verify rather than believe me: unzip the archive and search every file for fetch(. You will find four calls, all to roblox.com, and nothing else.

Is this safe for my account?

The honest answer is that a stored session cookie is as powerful as a password, so the risk is real and worth naming. Anything with access to that profile can read it, exported vault files are plain JSON, and a shared or public machine is a bad place for either. What the extension does not do is move that risk anywhere new: the cookie never leaves the device it was already on.

Will Roblox ban me for using it?

Having several accounts is not against the Roblox Terms of Use, and this extension does not automate play, inject anything into the game client or touch the economy. It re-uses a session you created yourself, on the same device, the way the site already expects. Using alternate accounts to evade a moderation action is a different matter and will get you banned regardless of how you switch.

Why does it ask for cookie permissions?

Because reading and writing one specific cookie is the entire feature. The manifest asks for cookies, storage and tabs, with host access limited to *://*.roblox.com/*. It cannot see any other site, and Chrome enforces that, not the extension's good intentions.

What happens to the account I am signed in to now?

Nothing, until you press Add current, which saves it. Switching replaces the live cookie with another one; the account you left is still in the vault and one click away. If you add an account twice it is matched on Roblox user id and updated in place rather than duplicated.

Can I move my vault to another computer?

Settings → Export vault writes a JSON file; Import vault reads it back and merges by user id. Treat that file exactly like a password manager export, because functionally that is what it is.

Why unpacked instead of the Chrome Web Store?

Store review for an extension whose job is handling session cookies is slow and often ends in a rejection. Loading it unpacked also means the code you run is the code you read: there is no build step and no minification between the zip and what runs.

Does it work in Firefox?

Not as shipped. The APIs used here have Firefox equivalents under the browser.* namespace, but Manifest V3 service workers and the install flow differ enough that it needs a separate build. This archive targets Chromium only.