Skip to main content

How to Set Up Image Domain

An image domain lets eligible Atomicat accounts serve page images from a branded subdomain such as cdn.yourbrand.com or images.yourbrand.com, separate from your main page URL. This is optional — most users publish successfully without it — but it helps high-traffic campaigns that want cleaner media URLs and branded asset delivery.

Use this guide when Connect Image Domain or Manage Image Domain appears in your Sites menu and you want to complete the DNS setup.

Before You Start​

Make sure you have:

  • A custom domain already connected and verified on the Atomicat site. See How to connect a custom domain.
  • Access to DNS for the same root domain (GoDaddy, Cloudflare, Hostinger, etc.).
  • Plan or module access that includes image domain features. If the menu option is missing, your account may not include this feature yet.
  • A chosen image subdomain that does not conflict with your live site host (for example cdn, images, or media).

Image domain setup happens in Sites, not in the Page Builder. DNS records are added at your domain provider, same as a custom domain.

Step 1: Confirm the Main Custom Domain​

  1. Open Sites in Atomicat.
  2. Find the site that should use the image domain.
  3. Confirm the custom domain is connected, verified, and showing SSL active when applicable.

The image domain attaches to a site that already has a working custom domain. If the main domain is still pending DNS, finish that workflow first.

See Connect a domain and DNS records for reference.

Step 2: Open Connect Image Domain​

  1. In Sites, locate the correct site row.
  2. Open the actions menu (three dots or equivalent) for that site.
  3. Click Connect Image Domain (or Manage Image Domain if you are updating an existing setup).

If you do not see this action, check plan access, connected domain status, or contact support — the feature is not available on all accounts.

Step 3: Enter the Image Subdomain​

  1. In the image domain dialog, enter the subdomain you want for images.
  2. Use a dedicated host label, such as:
ExampleUse when
cdn.yourbrand.comYou want a generic CDN-style subdomain.
images.yourbrand.comYou prefer a descriptive media subdomain.
media.yourbrand.comYou separate marketing pages from asset URLs.
  1. Confirm the subdomain does not match your main page URL unless Atomicat explicitly allows it.
  2. Copy the DNS record Atomicat shows — usually a CNAME with host and target values.

Copy values exactly. Do not add https:// or page paths.

Step 4: Add the DNS Record at Your Provider​

  1. Sign in to your domain provider or DNS manager.
  2. Open the DNS zone for yourbrand.com.
  3. Click Add record.
  4. Set Type to CNAME (or the type Atomicat shows).
  5. In Host or Name, enter only the subdomain label — for cdn.yourbrand.com, enter cdn.
  6. In Value or Target, paste the destination from Atomicat.
  7. Save the record.

Remove or update any conflicting record for the same host before saving.

Provider-specific domain guides:

Step 5: Verify the Image Domain in Atomicat​

  1. Wait a few minutes for DNS propagation (sometimes longer).
  2. Return to Atomicat Sites.
  3. Open the image domain flow again and click Verify or Check DNS.
  4. Confirm Atomicat reports the record as valid.

If verification fails, compare the CNAME in your provider with Atomicat character by character. Use DNS Checker to confirm the record is public.

Step 6: Test Images on a Live Page​

  1. Open a published page on the site that uses the image domain.
  2. Load the page in an incognito window to avoid cache.
  3. Confirm images load correctly and the page renders without broken media.
  4. Optionally inspect image URLs in the browser — they should reflect the configured image domain when the feature is active.

Republish the page if you changed image-domain settings while editing in the builder.

Best Practices​

  • Configure the main custom domain and SSL before the image domain.
  • Avoid changing image-domain DNS during active paid campaigns unless necessary.
  • Keep a screenshot of DNS settings before editing records.
  • Use a dedicated subdomain (cdn, images) rather than reusing www.
  • Test on mobile and desktop after verification.

Troubleshooting​

ProblemWhat to try
Connect Image Domain not visibleConfirm plan/module access, custom domain connected, and site permissions.
DNS verification failsMatch CNAME host and target exactly; wait for propagation; remove duplicate records.
Images still use old URLsRepublish pages; clear browser cache; wait for CDN propagation.
SSL warning on image URLsAllow time for certificate issuance after DNS verifies; recheck domain status in Sites.
Wrong site selectedImage domain is site-specific — confirm you configured the site that publishes your campaign pages.

Outcome​

Your Atomicat site can now serve images through the branded image subdomain you configured. Page URLs stay on your main domain while media delivery uses the dedicated image host — useful for performance-focused landing pages and cleaner campaign infrastructure.

FAQ​

Is an image domain required to publish pages?

No. Most users publish pages without configuring an image domain. It is an optional feature for eligible accounts.

Can I use the same subdomain as my main website?

Usually you should use a dedicated subdomain such as cdn or images. Follow the host Atomicat shows in the setup dialog.

Why do I not see Connect Image Domain?

The feature may depend on your plan, modules, connected custom domain, or account configuration.

Do I edit DNS inside Atomicat?

No. Add DNS records at your domain provider. Atomicat shows the values and verifies them.

Should beginners set up an image domain first?

No. Connect a custom domain, publish a page, verify SSL, and confirm tracking first. Add an image domain when your account supports it and your campaign needs it.