Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/rojo-rbx/rojo/llms.txt

Use this file to discover all available pages before exploring further.

rojo upload builds your project in memory and streams the result to the Roblox API, updating a live asset without writing a file to disk first. It supports two authentication methods: the legacy .ROBLOSECURITY cookie and the newer Open Cloud API key.

​
Synopsis

rojo upload [PROJECT] [OPTIONS]
--asset_id is always required. Which other flags you need depends on your chosen auth method.

​
Arguments and flags

​
PROJECT
string
Path to the project file or to a directory containing a default.project.json. Defaults to the current directory.
​
--asset_id
number
required
The asset ID (place ID or model ID) to upload to.
​
--cookie
string
Your .ROBLOSECURITY authentication cookie value. If omitted, Rojo attempts to find one automatically from the system (for example, from a running Roblox Studio installation). Used for legacy authentication.
​
--api_key
string
Open Cloud API key obtained from create.roblox.com/credentials. When provided, Rojo uses the Open Cloud API. Only supports uploading to a place.
​
--universe_id
number
Universe ID of the place to update. Required when using --api_key.

​
Global flags

​
--verbose / -v
boolean
Increase log verbosity. Pass multiple times (e.g. -vv) for more detail.
​
--color
string
default:"auto"
Control color output. Accepted values are auto, always, and never.

​
Authentication methods

Never commit or share your .ROBLOSECURITY cookie. It grants full access to your Roblox account. Prefer Open Cloud API keys for CI/CD pipelines.

​
Examples

Upload using Open Cloud from a specific project file: 
rojo upload path/to/my-game.project.json \
  --api_key <YOUR_API_KEY> \
  --universe_id 123456789 \
  --asset_id 987654321
Upload using a cookie found automatically by Rojo: 
rojo upload --asset_id 987654321

Build docs developers (and LLMs) love

Get started for freeTalk to us