---
title: "Get started for experienced creators"
url: /docs/en-us/onboarding
last_updated: 2026-11-16T17:23:46Z
description: "The core concepts of the Roblox engine for creators coming from other platforms, with guides for engineers, artists, file-based workflows, and Unity and Unreal comparisons."
---

# Get started for experienced creators

If your team already ships games on other engines or platforms, most of what you know carries over to Roblox. A few fundamentals work differently, and learning them first saves rework later. This section collects what you need in your first weeks on Roblox.

A few terms come up everywhere:

- **Game:** The overall project that players join. A game is a collection of places, and services like data stores, analytics, and in-game purchases are scoped to it.
- **Place:** A discrete scene or zone within a game, such as a lobby or a level. Each server runs one place.
- **Studio:** The editor you use to build places, write scripts, and upload assets. You edit one place at a time.
- **Cloud-first:** Places, assets, and scripts are saved to Roblox by default, rather than to files on your disk.

![The Roblox Studio user interface with markup to show the various windows and panels.](../assets/studio/general/Studio-Layout.png) ## Key differences from other engines

- **Cloud storage:** Studio saves your places, assets, and scripts to Roblox rather than to files on your disk, and your team edits them together in real time with [Team Create](/docs/en-us/projects/collaboration.md). If you want Git and other file-based tools, see [Compare file-based workflows](/docs/en-us/projects/file-based-workflows.md).
- **Multiplayer by default:** Every game runs on Roblox servers with a [client-server model](/docs/en-us/projects/client-server.md), so where you place an object or script determines whether the server, the client, or both can see and run it.
- **Built-in physics:** Parts simulate physics automatically without extra components, and you connect them to each other with [constraints](/docs/en-us/physics/mechanical-constraints.md).
- **Luau:** Scripts use [Luau](/docs/en-us/luau.md), a fast, gradually typed language derived from Lua.
- **Materials instead of shaders:** Roblox doesn't support custom shaders, so you build materials with `Class.SurfaceAppearance` and `Class.MaterialVariant` and create effects with built-in materials and instances.
- **Automatic quality scaling:** Roblox adjusts rendering, lighting, and streaming to each device, which lets the same game run on phones, consoles, and PCs.

## Onboarding by role

![A diagram of the Roblox client-server model.](../assets/scripting/client-server/Client-Server-Model.png) #### Engineering

The data model, scripting, replication, streaming, data stores, and performance.

[<h6>For developers</h6>](/docs/en-us/developers.md)

![A realistic mossy rock.](../assets/modeling/surface-appearance/SurfaceAppearance-Example-3.jpg) #### Art

PBR materials, mesh limits, lighting, characters, and rigs.

[<h6>For artists</h6>](/docs/en-us/artists.md)

## Engine comparisons

![The Unity user interface with markup to show the various windows and panels.](../assets/engine-comparisons/Unity-Editor-Layout.png) #### Unity

Map Unity concepts like GameObjects, components, and C# scripts to their Roblox equivalents.

[<h6>From Unity</h6>](/docs/en-us/unity.md)

![The Unreal Engine user interface with markup to show the various windows and panels.](../assets/engine-comparisons/Unreal-Editor-Layout.png) #### Unreal

Map Unreal concepts like actors, Blueprints, and C++ to their Roblox equivalents.

[<h6>From Unreal</h6>](/docs/en-us/unreal.md)

## Team workflows

- [Compare file-based workflows](/docs/en-us/projects/file-based-workflows.md): Use Git with Roblox, from Script Sync to fully managed Rojo, and set up dev, stable, and production environments.
- [Collaboration](/docs/en-us/projects/collaboration.md): Edit places together in real time with Team Create.
- [Groups](/docs/en-us/projects/groups.md): Own games and assets as a team, and manage roles and permissions.
- [Packages](/docs/en-us/projects/assets/packages.md): Version and reuse content across places and games.

## Next steps

- [Install and set up Studio](/docs/en-us/studio/setup.md).
- Speed up development with AI. Most professional developers will want to use their own AI tools and agent harness, and connect them to the [Studio MCP server](/docs/en-us/studio/mcp.md) so they can build and test in Studio. [Assistant](/docs/en-us/assistant/guide.md) is Studio's built-in alternative.
- Learn how players find and play your game in [Discovery](/docs/en-us/discovery.md).