Skip to main content
Four settings decide what a player sees, from the link they open to the screen they play on. Set them once for the studio, and every playtest, survey, waitlist, NDA, and key vault picks them up.

Take the guided tour

Set the logo, colors, and background players see on every screen.

What you need first

  • Your game’s name, and the URL slug you want players to see.
  • A logo, a background image, and a favicon. PNG, JPG, or WebP.
  • Your hex colors, for buttons, button text, and accents.
  • Admin or owner access, and a plan that includes studio customization.

The playbook

1

Set the game identity

Go to Branding > Game.
  • Set Game name, which players see through onboarding, briefings, and every published surface.
  • Set the platform and genres, if you want testers to know what to expect.
2

Claim the public URL

Set your public URL on the same tab. It becomes the first path segment of every player link.
Changing it later breaks every link you have already shared, and there are no redirects. Settle on it before you start recruiting.

Game settings

Game identity and the public URL behind every player link.

Share links

What a player link looks like once this slug is settled.
3

Upload the logo and background

Go to Branding > Branding.
  • Upload the Logo shown at the top of every published surface.
  • Upload the Background that sits behind every session.
  • Lower Backdrop opacity if busy key art competes with the text on top of it.

Branding

Every field, its limits, and what happens when you clear one.

Plans and limits

Which plans include studio customization at all.
4

Set the colors and favicon

On the same tab, set button color, button text color, and accent color as hex values, and upload a square favicon.Clear any field to fall back to the theme default.
5

Write the link preview

Go to Branding > Social and set the image, title, and description.Write the title for someone who has not clicked yet. Saying what you are testing pulls better than repeating the game name.

Social preview

The card your links unfurl into, and the generated fallback.

Resource announcements

Where the same artwork lands when you post to a channel.
6

Check it as a player would

Open a playtest and use its preview to walk the flow end to end.The preview shows the same brand a published surface will, so this is the honest check.

Preview the flow

What preview covers, and the stages it silently skips.

Session flow

Every branded screen a player meets, in order.
7

Match the emails to it

Player emails are branded separately, in Branding > Emails.

What players see if you set nothing

Nothing goes blank. A studio with no uploads gets the Userplay mark, a shared default backdrop, the default favicon, and the theme’s colors. A missing social image is generated from your background and logo. You can set these in any order, and fill the gaps later.
The logo in your own sidebar is a separate setting, in Settings > Studio. Players never see it.

How you know it worked

  • The branding editor previews each change before you save.
  • A playtest preview opens with your logo, background, and colors rather than the defaults.
  • Pasting a player link into Discord or Slack unfurls your social card.
  • The browser tab on a player-facing page shows your favicon.

Branding

Every field, its limits, and what happens when you clear one.

Game settings

Game identity and the public URL behind every player link.

Social preview

The card your links unfurl into, and the generated fallback.

Brand the emails players get

Playbook: the other half of the player-facing brand.