---
id: "docs.en.studio-play"
translation_of: "docs.studio-play"
title: "Studio: play the current game"
product: "studio"
scope: "studio"
locale: "en"
audience: ["game-designer","educator"]
content_type: "guide"
summary: "Run the authored definition in the real play engine and understand local, backend, multiplayer, lobby, and private-piece behavior."
topics: ["studio","play","use","check"]
tasks: ["play-local-game","play-backend-game","use-multiplayer-lobby","check-private-pieces"]
aliases: ["play local game","play backend game","use multiplayer lobby","check private pieces"]
prerequisites: ["docs.getting-started"]
related_ids: ["docs.studio-workspace","docs.studio-testing-feedback","docs.studio-simulation"]
canonical_url: "https://mijnspel.com/docs/en/studio-play/"
alternate_urls: {"en":"https://mijnspel.com/docs/en/studio-play/","nl":"https://mijnspel.com/docs/nl/studio-play/","de":"https://mijnspel.com/docs/de/studio-play/"}
source_provenance: ["studio-dashboard/src/play-mode.js","studio-dashboard/src/viewer.js","studio-dashboard/widgets/lobby.js"]
test_provenance: ["studio-dashboard/cypress/e2e/66b_token_content.cy.js","studio-dashboard/cypress/e2e/60_editor_workspace.cy.js"]
last_verified_commit: "22d2b3d1b5177fb46f81616a5042b47d54a0e38b"
last_verified_date: "2026-08-21"
---
# Studio: play the current game {#studio-play}

Play uses the same engine and authored board as Build while hiding editing controls. Use it after structural or controller changes to confirm WYSIWYG behavior, legal actions, setup, reset, and end conditions.

## Local and backend games {#local-backend}

Frontend-only games run locally and can support same-device or hot-seat play. A solo game with a backend synchronizes and persists through its backend contract. A successful canvas edit does not guarantee either path; exercise reload and a complete turn.

## Networked multiplayer and lobby {#multiplayer-lobby}

A networked game needs exactly one explicit platform lobby widget in its board definition. The platform supplies status, share link, copy action, and join-by-code form. Do not hand-write lobby HTML and do not add the widget to solo or single-device games.

## Viewer privacy {#private-pieces}

Private pieces are filtered for the current viewer. Test with separate browser sessions and distinct seats rather than relying on the owner view. Keep private information out of public labels and client-visible debug text. Continue with [Testing and feedback](/docs/en/studio-testing-feedback/).