> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/publishing/sharing-vs-publishing.md).

# Sharing vs Publishing

Uploading your project and publishing it are not the same thing. Understanding the difference determines who can access your game, how they can find it, and when it becomes public. Getting this wrong in either direction — sharing something you meant to keep private, or holding back something that is ready — is easy to avoid once the two states are clear.

## The Core Explanation

### Uploaded and unpublished: shareable, not public

When you upload your project, it appears on your Sandbox Studio home page under `Yours`. At this stage, your game exists on the platform but is not visible to anyone browsing `Discover`. The public cannot find it, search for it, or access it through the platform.

What you can do is share it directly. The project URL — copied from your browser when you open it from the dashboard — works for anyone you send it to. No account is required to access it. This makes the unpublished state the right place for testing and feedback: you control exactly who sees it by controlling who has the link.

How to upload and copy that link: [Uploading Your Project](/publishing/uploading-your-project.md).

{% hint style="info" %}
*TIP: Use the unpublished state for all playtesting. Send the link to your testers, gather feedback, make changes, and re-upload. Nothing goes public until you actively choose to publish.*
{% endhint %}

### Published: accessible to everyone

When you publish your game, it becomes publicly accessible on Sandbox Studio. Anyone browsing `Discover` can find and play it — not just people with the direct link. The direct link continues to work, but the game is now discoverable by the general public.

Publishing is a deliberate action. It is not triggered by uploading, and it does not happen automatically. You choose when to make that switch.

How to turn publishing on, update a live game, or unpublish: [How to Publish](/publishing/how-to-publish.md) and [Updating and unpublishing your game](/publishing/updating-and-unpublishing-your-game.md).

### The publish control

The control is a toggle labelled `Published` on the `Edit Game` panel. It is not a checkbox labelled Publish.

![The Published toggle is at the top of the Edit Game panel.](https://content.gitbook.com/content/WgFjStdWWXj1Wc6xnrcJ/blobs/DDPfSQaodrqjqOcm8duY/Unknown%20image)

{% hint style="info" %}
*NOTE: Once published, your game is immediately accessible to the public. Make sure your name, tags, and thumbnail are set before turning `Published` on — these are the first things a new player will see.*
{% endhint %}

## Practical Guidance

* Use the unpublished state for all testing and feedback — the direct link gives you full control over who accesses the game.
* Only publish when the game is ready for a public audience. Publishing is not reversible without turning `Published` off and saving.
* Before publishing, complete the project settings — name, tags, and thumbnail. An incomplete listing reflects poorly on the game before anyone has played it.
* The direct link works in both states. Sharing the link does not mean the game is public. Public means it is discoverable on the platform without a link.

## Common Mistakes

| Mistake                                                   | What to do instead                                                                                  |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Assuming uploading makes the game public                  | Uploading only makes it visible to you on your dashboard — publishing is a separate action          |
| Publishing before filling in name, tags, and thumbnail    | Complete the project settings first; they are what the public sees before they play                 |
| Sharing the direct link and assuming that makes it public | The link bypasses discoverability — the game is only truly public once the `Published` toggle is on |
| Forgetting the direct link still works after publishing   | The link continues to work; anyone with it can still access the game directly                       |

Uploaded means it exists on the platform. Published means it is open to everyone. The distinction gives you a safe space to test and refine before committing to a public release — use it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://studio-docs.sandbox.game/publishing/sharing-vs-publishing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.