Studio on Windows, local Web and Cloud
Studio has three distinct ways to open a project. Choose based on where the source files must remain; selecting the language does not change storage or access permissions.
Windows desktop
The Windows application uses the native project folder picker. Open an existing Obsidrel directory or create content in a compatible project. YAML and assets are saved locally with backup and conflict checks. Find available installers through the Studio page, where the published Stable, Beta and Dev channels are listed when a verified installer exists. A missing channel is not a download failure.
Local browser workspace
The separate localhost development service uses an authorized folder in a browser supporting the File System Access API (typically Chromium). Grant read/write access to the original project directory. The folder handle is used only after an explicit user permission gesture; the bridge uses a constrained local session for inspection. The project itself is saved to the authorized local directory, not automatically to your Marketplace Cloud account.
This local workflow requires a local bridge and is not the same as visiting /studio/web. If you select only resources/, YAML editing can work but pack assets require the parent project folder containing pack/.
Hosted Studio Web Cloud
Visit /studio/web from the Marketplace when Studio Cloud has been enabled for your account. Sign in first. The project portal creates, opens and manages account-owned projects, and the editor is served separately under /studio/web/app/. Cloud writes, backups and source ZIP exports operate on the remote project workspace; opening the Cloud editor does not import your computer files by itself.
Access may be restricted during maintenance, staged previews or entitlement checks. A public Studio marketing page does not guarantee that the hosted editor is currently enabled for every account.
What stays common
The Windows and Web editions share the same content editors and validation rules, with a bounded Rust project engine behind platform-specific access. Switch language in the Studio preferences (English by default; Brazilian Portuguese supported). Regardless of mode, save explicitly, review warnings and test Minecraft behavior with the matching Core.
Continue with First steps, Cloud projects and Backup and conflicts.