Skip to content

Brand Guidelines

We want developers to build tools, libraries, runtimes, integrations, and other projects for (or with) Luau, to be able to clearly describe those projects as working with Luau. At the same time, people should be able to easily distinguish projects that are part of Luau itself from independent projects created by the community.

“Luau” and its logo are trademarks of Roblox Corporation. Roblox develops and maintains Luau as an open-source programming language. These guidelines describe how community members may use the Luau name and logo in their own projects.

You are welcome to use the Luau name to accurately describe your project or its compatibility with Luau.

For example:

  • Foo, a Luau development tool
  • Foo, a package manager for Luau
  • Luau support for Foo
  • Foo’s Luau integration

These uses don’t require permission.

Independent projects should have their own distinctive identity, and should not use a name that could reasonably make the project appear to be an official component, product, or service of Luau (unless that use has been explicitly approved by the Luau team).

In particular, avoid using Luau followed by a generic product or technology category as the name of an independent project.

For example, names such as these could reasonably be interpreted as official Luau projects:

  • Luau Runtime
  • Luau SDK
  • Luau Studio
  • Luau Compiler

Instead, give the project its own name and describe its relationship to Luau separately:

  • Foo, an alternative runtime compatible with Luau
  • Bar, a package manager for Luau

The same principle applies to acronyms, organization names, and other branding where the overall presentation could reasonably suggest that a project is part of Luau. This also includes domain names (e.g., “luau[product].com”) and social media accounts where the name or handle could imply that it’s an official product.

Using the Luau name in a repository, package, module, or other technical identifier is generally fine when it is descriptive and the surrounding project has a clear independent identity that users can identify.

You are welcome to refer to Luau when describing software based on or derived from Luau, subject to the applicable open-source licenses.

If a project makes significant changes to Luau, its presentation should make those changes clear and should not imply that the modified version is an official Luau release.

For example: “Foo, a runtime based on Luau” is preferable to presenting a substantially different runtime simply as Luau.

The Luau logo may be used to refer to Luau where permitted by its applicable license and guidelines.

Third-party projects should not use the Luau logo, or a confusingly similar variation of it, as their own primary identity in a way that suggests the project is officially produced or endorsed by Luau.

Separately, Luau’s Hina mascot was created by Alex Mullins and is licensed under Creative Commons Zero (CC0).

Any project that uses the Luau name should include the following attribution: “Luau is a trademark of Roblox Corporation.” A statement such as “Independent project; not affiliated with or endorsed by Roblox or the Luau team” can also help make a project’s relationship to Luau clear. However, a disclaimer may not be sufficient where the project’s name or overall presentation would otherwise reasonably appear to be an official Luau product.

These guidelines are intended to make it easy to build things for Luau, not to prevent people from talking about or supporting the language.

If you’re unsure whether a name or use of Luau is appropriate, reach out to us at legal@roblox.com. We’re happy to work with community projects to find an approach that is clear without being unnecessarily disruptive.

Where an existing community project needs to change its branding to follow these guidelines, we’ll aim to work with its maintainers on a reasonable transition.

Roblox reserves the right to update these guidelines and to take appropriate action regarding any use of the Luau name or logo that does not comply with them. As mentioned above, we’ll work with existing projects on a reasonable transition timeline.