How to connect your own domain

Want visitors to see yourbusiness.com instead of yoursite.playcode.io? This guide walks you through it step by step. No technical knowledge needed - just follow along.

Before you start: You need a Pro account and a published project. Custom domains are a Pro feature.

First: which kind of project are you connecting?

Playcode has two ways to publish, and the DNS setup is slightly different for each. Pick the one that matches your project:

Project type What it is
Static site
(Playcode Pages)
A single-page site, landing page, portfolio, or anything built with HTML + JS that runs entirely in the browser. Your published URL looks like my-site.playcode.io. → Jump to DNS setup for static sites
Cloud app
(Playcode Cloud)
A full-stack app with a backend, database, file uploads, or anything that runs server-side. Your published URL looks like my-app.playcode.ai (notice the .ai - different from Pages above). → Jump to DNS setup for cloud apps
Not sure? Look at the URL your project shows when published. If it ends in .playcode.io, you have a static site (Pages). If it ends in .playcode.ai, you have a cloud app.

Where to buy a domain (if you don't have one yet)

We recommend Cloudflare Registrar. It is the easiest option for Playcode users:

  • Cheapest prices - Cloudflare sells domains at cost, no markup
  • CNAME flattening - works perfectly with root domains (more on this below)
  • Simple DNS management - everything in one place
  • No upsells - just a clean, reliable service

Other popular options: Namecheap, Google Domains, GoDaddy. They all work with Playcode, but Cloudflare makes the DNS setup easiest.

Important for everyone: Do the DNS step BEFORE adding the domain in Playcode. It makes everything go smoother.

Static sites - DNS setup

For Pages projects (*.playcode.io), all sites share one Playcode server. You'll point your domain at app.playcode.io.

Option A: CNAME record (recommended)

This is the best option. Use it if your domain provider supports it.

Setting What to enter
TypeCNAME
Name@ for root domain (yourbusiness.com)
www for www.yourbusiness.com
Targetapp.playcode.io
About root domains and CNAME: Technically, the DNS standard does not allow CNAME records on root domains (yourbusiness.com without www). However, Cloudflare supports this through a feature called "CNAME flattening" - it just works. Most other providers (GoDaddy, Namecheap) do not support CNAME on root domains. If your provider does not support it, use Option B below.

Option B: A record (if CNAME doesn't work for root domain)

If your domain provider does not allow CNAME on the root domain, use an A record instead. This points your domain directly to our server's IP address.

Setting What to enter
TypeA
Name@
Value88.198.232.54
Note about A records: A records point to a specific IP address. If we ever need to change our server IP in the future, you would need to update this record. CNAME (Option A) does not have this problem because it points to a name, not an IP. This is why CNAME is always preferred when your provider supports it.

Tip: If you are using GoDaddy or Namecheap and want to use your root domain, the easiest solution is to transfer your domain to Cloudflare (it is simple and usually takes a few minutes). Then you can use CNAME for everything.

Cloud apps - DNS setup

For Cloud projects (*.playcode.ai), point your domain at Playcode's Cloud custom-domain IP. Do not CNAME your domain to your project subdomain. The project subdomain is only the default Playcode URL; custom domains route through the dedicated custom-domain edge.

Cloud custom-domain IP: 188.40.16.17. This is the stable production IP for Cloud app custom domains.

A record for root domain

Use this if you want yourbusiness.com to open your Cloud app.

Setting What to enter
TypeA
Name@
Value188.40.16.17

A record for www

Add this too if you want www.yourbusiness.com to open the same Cloud app.

Setting What to enter
TypeA
Namewww
Value188.40.16.17
Cloudflare users: set these records to DNS only (gray cloud). If Cloudflare proxying is on, Cloudflare will try to serve the certificate instead of Playcode's Cloud edge.

Provider-specific instructions

These steps assume you've already picked the right target from above (app.playcode.io for static sites, or 188.40.16.17 for Cloud apps). Replace <target> with whichever applies to you.

Cloudflare (recommended)
  1. Log in to Cloudflare and select your domain
  2. Go to DNS > Records
  3. Click Add record
  4. Select Type: CNAME for static sites, or Type: A for Cloud apps
  5. Name: Enter @ (for root) or www
  6. Target / IPv4 address: Enter <target>
  7. Proxy status: Click the orange cloud to turn it gray (DNS only)
  8. Click Save
Very important: The cloud icon must be gray (DNS only), not orange. If the proxy is on, your SSL certificate will not work.
GoDaddy
  1. Log in to GoDaddy > My Products
  2. Click DNS next to your domain
  3. Click Add
  4. For static sites: Type = CNAME for www, or Type = A for root domains
  5. For Cloud apps: Type = A, Name = @ or www, Value = 188.40.16.17
  6. Click Save
GoDaddy does not support CNAME on root domains. Static sites can use the static-site A record for the root. Cloud apps should use A records for both root and www.
Namecheap
  1. Log in to Namecheap > Domain List > Manage
  2. Go to Advanced DNS tab
  3. Click Add New Record
  4. For static sites: Type = CNAME for www, or Type = A for root domains
  5. For Cloud apps: Type = A, Host = @ or www, Value = 188.40.16.17
  6. Click the green checkmark to save
Namecheap does not support CNAME on root domains. Static sites can use the static-site A record for the root. Cloud apps should use A records for both root and www.

Step 2: Add domain in Playcode

Wait 5-10 minutes after changing DNS, then:

  1. Open your project in Playcode
  2. Click Publish in the top right corner
  3. Scroll down to Custom Domain
  4. Click Attach
  5. Type your domain name exactly as you set it up:
    • yourbusiness.com - if you configured the root domain
    • www.yourbusiness.com - if you configured the www subdomain
  6. Click Attach
Common mistake: Only enter the domain name. Do not enter your project name, and do not add https:// in front.
  • Correct: yourbusiness.com
  • Wrong: https://yourbusiness.com
  • Wrong: my-project-name

Step 3: Wait for SSL (automatic)

After adding your domain, Playcode does two things automatically:

  1. HTTP access - your site works immediately at http://yourbusiness.com
  2. SSL certificate - HTTPS is generated automatically. Cloud apps usually take under a minute; static sites take 1-2 hours (sometimes up to 24 hours). No action needed from you.

Once SSL is ready, your site works securely at https://yourbusiness.com.

Something not working?

Site not loading at all

  • DNS changes can take up to 30 minutes to spread. Wait and try again.
  • Double-check that your DNS record points to the right target for your project type (app.playcode.io for static sites, 188.40.16.17 for cloud apps).
  • Make sure you entered the domain correctly in Playcode (no typos, no https://).

HTTPS not working after the expected time

  • Cloudflare users: Make sure the proxy is OFF (gray cloud, not orange).
  • Check that HTTP works first (http://yourbusiness.com). SSL is generated after HTTP works.
  • For Cloud apps, make sure both root and www use A records to 188.40.16.17.

"Domain not valid" error

  • Enter just the domain: yourbusiness.com or www.yourbusiness.com
  • Do not enter your project name, random words, or URLs with https://

Quick summary

Project type + situation What to do
Static site on Cloudflare CNAME @ or www > app.playcode.io (proxy off)
Static site, GoDaddy/Namecheap root domain A record @ > 88.198.232.54
Cloud app on Cloudflare A record @ and www > 188.40.16.17 (proxy off)
Cloud app, GoDaddy/Namecheap root domain A record @ and www > 188.40.16.17

Still stuck? Chat with us using the chat button in the bottom right corner. We'll help you get your domain connected.

Need more help?

Can't find what you're looking for? Chat with us or send us an email.