Rojo Compatibility

Azul features a Rojo Compatibility Mode that allows you to build or push Rojo-style projects into Roblox Studio.

When this article refers to “Rojo-style” projects, it means that the project is structured similarly to Rojo and its project format. In practice, this means the feature will also work with tools like Argon. Note that full support for these tools is not guaranteed.

azul build --rojo
azul build --rojo --rojo-project default.project.json
azul push -s Packages -d ReplicatedStorage.Packages --rojo

In this mode, Azul will try to do the following:

• Read the default.project.json (or the provided project file) to interpret Rojo-style structure.
• If no default.project.json is provided, or none is found, Azul will attempt to interpret the Rojo-style structure and push it into Studio.

Tip

Azul is capable of reading nested project files, so you can have a default.project.json in your root folder and another one in a subfolder. The subfolder’s project file will be used for that subfolder’s contents.

Supported Rojo features

This is a comprehensive list of Rojo features supported in the Rojo Compatibility Mode, with the following classification:

• ✅ - The feature is fully supported and works as expected
• ❌ - The feature is not available because it does not makes sense to include it
• 🔜 - The feature is not available but it’d be nice to include it at some point
• 🤷‍♀️ - The feature is not available yet; open to discussion about implementing this

Feature	Status	Notes
Scripts & folders (*.server.luau, *.client.luau, *.module.luau)	✅
Rojo Project Files	✅	Nested project files are also supported.
JSON Models (*.model.json)	✅
XML or binary Models (*.rbxm, *.rbxmx)	❌	For advanced use-cases, directly build your project using rojo build.
Meta Files	❌	Supporting meta files would unecessarily complicate the build process for Rojo projects.
Plain text files (*.txt)	🤷‍♀️
Localization Tables (*.csv)	🤷‍♀️
TOML Modules	🤷‍♀️