Tabletop Simulator, developed and published by Berserk Games, is a tabletop physics sandbox. The first challenge is not learning one board game’s rules; it is learning how to move the camera, handle pieces, save the table, and run a room without letting the table turn into a mess.
This guide is for a first clean private table or simple Classic/DLC session. It is not a guide to any specific Workshop game, public lobby, copyrighted recreation, custom asset import workflow, Lua scripting, TTRPG campaign setup, VR setup, or official DLC ruleset.
Essential Tips
1. Run The Tutorial Before Inviting Friends
The controls matter more than the table you pick.
Tabletop Simulator has many object and camera actions, and the official controls page recommends trying the in-game tutorial first. Spend a few minutes learning camera rotation, zoom, object pickup, flipping, and Alt zoom before you try to teach a game to other players.
2. Start With A Simple Table
A clean setup makes the sandbox readable.
Use a Classic table, an official DLC table you understand, or a simple trusted setup for your first session. Avoid a heavily scripted Workshop table until you know what the base game does on its own, because scripts, zones, custom assets, and table rules can change the experience.
3. Master The Camera Before Moving Pieces
Most early frustration is bad camera control.
Use right mouse to rotate the view, middle mouse to pan, scroll to zoom, WASD to pan, Z to quick-zoom, and spacebar to reset your camera. Get comfortable moving around the table before you grab a deck, die, token, or miniature.
4. Use Alt Zoom For Cards And Small Objects
Inspect the piece before you pick it up.
Hover over an object and use Alt zoom when you need to read a card or inspect a small component. In games with hidden information, be careful with peek actions and hand zones, because other players may be alerted or the table may have scripted visibility rules.
5. Practice One Object Loop
Pick up, drop, flip, rotate, then repeat.
Start with one card, die, token, or piece. Pick it up with left mouse, drop it, flip it, rotate it, and right-click it to see its context menu. Then try box-selecting multiple objects and grouping them only after the single-object loop feels natural.
6. Lock Important Table Pieces
Accidental drags can ruin a setup.
Use the context menu’s Lock toggle on boards, mats, reference cards, scripted controls, and table fixtures that should not move. Leave movable pieces unlocked, but lock the things that define the play area.
7. Save Clean Table States
A good save is your undo button between sessions.
The Games menu supports Save & Load. Create a clean setup save before play begins, then save useful mid-game states when the table is stable. Do not wait until pieces are scattered, hands are wrong, or a scripted setup has been disturbed.
8. Respect Hand Zones
Hands are seats, hiding areas, and deal targets.
Hand zones are tied to player colors and can hold or hide cards and objects. If cards are not dealing or hiding correctly, check whether the table has the right seats, colors, and hand-zone behavior before blaming the deck.
9. Set Permissions Before Opening The Room
Hosts are responsible for what players can do.
The host can control permissions for table flipping, context menus, scaling, locking, peeking, nudging, zones, notes, saving, and more. In a learning room, restrict disruptive actions until everyone knows the table.
10. Use Turns When Order Matters
The sandbox will not enforce every game’s rules for you.
Options > Turns can track turn order, skip empty hands, allow pass turns, and optionally block out-of-turn interactions. Use it for games where player order matters, especially with newer players.
11. Keep Workshop Use Narrow
Every Workshop item is its own table.
Workshop content can add games, assets, scripts, components, and custom layouts. Subscribe to a small number of items, test them one at a time, and avoid assuming that a popular or recent item is current, authorized, complete, or beginner-friendly.
12. Prefer Private Rooms While Learning
Public play adds host rules, voice/chat norms, and table-specific behavior.
Tabletop Simulator supports public and private online games through Steam connections, and v14.2 changed underlying networking. For a first session, use a private game with people who can pause, explain, and recover from mistakes.
Controls and Table Habits
| Habit | Why It Helps | Beginner Use |
|---|---|---|
| Reset the camera | Prevents disorientation | Tap spacebar when the view gets awkward |
| Use Alt zoom | Reads cards without moving them | Inspect text before picking up a card |
| Right-click objects | Reveals table-specific actions | Find flip, rotate, lock, save, deck, and dice options |
| Lock fixtures | Protects the setup | Lock boards, mats, and scripted controls |
| Group deliberately | Moves sets together | Use grouping only when the pieces should stay together |
| Draw with number keys when supported | Avoids grabbing an entire deck | Hover over a stack/deck and type the draw count |
| Save clean states | Makes recovery easier | Save setup and stable mid-game positions |
| Use zones carefully | Controls seats, hands, hiding, randomization, and layouts | Do not resize or delete zones unless you are hosting and know why |
Hosting and Permissions
- Host the first room yourself: Even single-player starts count as hosted games, and hosting gives you control over options, permissions, saves, and table recovery.
- Promote only trusted helpers: Promoted players can do many host-level actions, so use promotion for someone helping run the table, not for every guest.
- Limit disruptive permissions early: Table flipping, locking, scaling, contextual access, peeking, zones, and saving can all affect the table state.
- Use player colors intentionally: Colors connect players to seats and hand zones. Make sure everyone is seated correctly before dealing or hiding information.
- Treat Game Master visibility as special: The black Game Master seat can see hidden information, so use it only when a game actually needs a GM.
- Check DLC ownership before host changes: Official DLC behavior can depend on the host owning the DLC, so do not move host during a DLC session unless you know the new host has access.
- Set voice and chat expectations: Use push-to-talk, team talk, private team channels, or text chat deliberately instead of letting communication become another rule dispute.
Workshop and Multiplayer
- Use Classic and DLC tables to learn the platform: They give you a cleaner path to controls, saves, hands, and permissions than an unknown scripted Workshop table.
- Subscribe slowly: Add one Workshop table or asset pack, test it, then add another. A large pile of subscriptions makes it hard to tell which item broke or changed a table.
- Do not treat someone else’s mod as your own: Save personal changes locally when you need a house setup, and only share work you are allowed to share.
- Avoid specific Workshop recommendations in a beginner guide: Availability, rights, maturity labels, dependencies, scripts, and compatibility can change.
- Expect public rooms to vary: Hosts can set different permissions, rules, voice/chat norms, promoted users, and table states.
- Remember LAN is not the normal path: The official technical page describes online play through Steam connections and says LAN play is not supported.
- Check networking assumptions after major updates: v14.2 moved multiplayer code paths to newer Steam networking APIs, so connection and hosting behavior can change.
Common Mistakes to Avoid
-
Do not invite everyone before learning the camera - A confused host slows down the whole table.
-
Do not grab a deck when you meant to draw one card - Use supported draw actions, hand zones, or context options instead of dragging the whole stack around.
-
Do not leave boards and mats unlocked - One accidental drag can shift the whole play area.
-
Do not resize, delete, or move zones casually - Hand, hidden, randomize, and layout zones can control seats, hidden information, and setup automation.
-
Do not promote every player - Promotion gives broad table control and can bypass normal permission limits.
-
Do not leave table flipping enabled in a learning room - Keep disruptive actions off until the group actually wants them.
-
Do not overwrite your clean setup with a messy save - Keep a stable setup save before saving mid-game progress.
-
Do not open a complex Workshop table as your first lesson - Learn the base controls before adding scripts, custom assets, and table-specific automation.
-
Do not assume public rooms use the same rules as yours - Host permissions, communication, seats, DLC, and table scripts can differ.
-
Do not move host during a DLC game without checking access - Official DLC play can depend on host ownership.
Summary
| Category | Top Tip |
|---|---|
| First session | Run the tutorial, then use a simple private table |
| Camera | Learn right mouse, middle mouse, scroll, WASD, Z, and spacebar |
| Inspection | Use Alt zoom before moving cards or tiny pieces |
| Objects | Practice pickup, drop, flip, rotate, and context menu actions |
| Stability | Lock boards, mats, and scripted controls |
| Saves | Keep a clean setup save and stable mid-game saves |
| Hands | Make sure seats/colors/hand zones are correct before dealing |
| Hosting | Set permissions before inviting players |
| Turns | Enable turn tracking when player order matters |
| Workshop | Subscribe slowly and avoid relying on specific items |
| Multiplayer | Prefer private rooms while learning |
Did this answer your question?
Your feedback helps keep the useful answers visible.Sources
8 checked for this guideEvery factual claim in this guide was checked against at least two independent sources before publication. These are the references used for Tabletop Simulator.
Next answers
Community notes0
No community notes yet.
Sign in to contribute