Skip to main content
The Cookies tab provides a dedicated interface for managing .ROBLOSECURITY cookies across all stored accounts — independent from the Accounts tab.
Each row in the cookie table represents one stored account:

​
Refreshing Cookies

​
Manual Refresh

Click the Refresh button on any row to immediately re-validate and obtain a fresh cookie for that account. The result is logged in the Logs tab.

​
Bulk Refresh

Click Refresh All to queue every stored cookie for refresh. Refreshes run sequentially with a configurable delay between each one.
A background thread silently refreshes all cookies on a repeating schedule:
Auto refresh runs entirely in the background — you don’t need to do anything. A log entry is written each time a cookie is successfully refreshed or fails.
Botify uses the auth ticket exchange method to obtain fresh cookies without requiring a new login:
1

Generate CSRF Token

Requests a CSRF token from the Roblox API using the existing .ROBLOSECURITY cookie.
2

Exchange for Auth Ticket

Uses the CSRF token + existing cookie to request a Roblox auth ticket.
3

Obtain Fresh Cookie

Exchanges the auth ticket for a brand-new .ROBLOSECURITY cookie.
4

Update MongoDB

Saves the fresh cookie to the botify_cookies collection, updating the age timestamp.
Cookies that have been fully invalidated (account banned, manually logged out, or password changed) cannot be refreshed this way. They will be marked Expired and must be re-added via the Accounts tab using Browser Login or Cookie Paste.