Custom Domain

Use your own domain for your forms instead of the default makeform.ai domain.

What you get with custom domains:

• ✅ Professional branded form URLs (e.g., forms.yourcompany.com)
• ✅ Automatic SSL certificates for secure HTTPS connections
• ✅ Quick setup with just one CNAME record

Step 1: Access the Domains Page

Navigate to the Domains section from your dashboard sidebar.

1. Log in to your Makeform account
2. Click on Domains in the left sidebar navigation
3. Click Add Your First Domain (or Add Domain if you already have domains)

Step 2: Choose Your Domain Type

Select whether you want to use a subdomain or root domain.

Step 3: Enter Your Domain

After selecting your domain type, enter your domain details.

Click Add Domain to proceed.

Step 4: Add CNAME Record to Your DNS Provider

After adding your domain, you’ll receive DNS configuration instructions.

How to Add the CNAME Record

1. Log in to your domain provider (e.g., GoDaddy, Namecheap, Cloudflare, Google Domains)
2. Navigate to DNS settings (usually called “DNS Management”, “DNS Records”, or “Advanced DNS”)
3. Add a new record with the following details:
   • Type: CNAME
   • Name/Host: Your subdomain (e.g., forms)
   • Value/Target: cname.makeform.ai
   • TTL: Auto or 3600 (1 hour)
4. Save the changes

Important Notes

• DNS propagation: DNS changes can take up to 24 hours to propagate globally, though most changes are visible within 1-2 hours
• SSL certificates: Will be automatically provisioned once DNS is configured
• Verification: You can check verification status using the “Check Verification” button

Step 5: Verify and Wait for Completion

Once DNS is configured, click Check Verification to verify your domain.

Verification Process

1. Wait 5-15 minutes after adding the CNAME record
2. Click Check Verification button in your dashboard
3. If DNS has propagated, the domain will be verified
4. SSL certificate will be automatically provisioned

Domain Status Indicators

Your domain will show different statuses during the setup process:

When Complete

You’ll see:

• ✅ Status changes to Verified (green checkmark)
• ✅ Message: “Domain is verified and ready to use!”
• ✅ Timestamps for Added, Last Checked, and Verified dates

Using Your Custom Domain with Forms

Once your domain is verified, you can assign it to your forms to create professional branded URLs.

Assign Custom Domain to a Form

Navigate to the Share page of the form you want to use with your custom domain.

1. Open your form in the form builder
2. Click on the Share tab in the top navigation
3. Find the Custom Domain section
4. Click the domain dropdown to select from your verified domains

After selecting a domain, your form will be accessible at:

https://yourdomain.com/f/{form-id}

For example: https://forms.company.com/f/abc123

Customizing Form URLs with Custom Paths

Take your branded URLs to the next level by creating clean, memorable paths instead of using the default form ID format.

What are Custom Paths?

Custom paths let you replace the /f/{form-id} format with your own custom URL path:

• Default format: https://yourdomain.com/f/abc123xyz
• Custom path: https://yourdomain.com/contact
• Another example: https://yourdomain.com/feedback

Enable Custom Paths

After assigning a custom domain to your form, enable the custom paths feature.

1. In the form Share page, locate the Custom Paths toggle
2. Click the toggle to enable custom path URLs
3. The custom path input field will appear

Create Your Custom Path

Enter your desired path and save it to create a branded URL.

1. Enter your path in the input field (e.g., contact, feedback, apply)
2. The system will validate your path in real-time:
   • ✓ Green checkmark — path is available
   • ✗ Red X — path is taken or invalid
3. Preview your URL below the input field
4. Click Save Path to create the custom path

Path Rules and Guidelines

When creating custom paths, follow these rules:

Allowed characters:

• Letters (a-z, A-Z)
• Numbers (0-9)
• Hyphens (-)
• Underscores (_)
• Forward slashes (/) for nested paths

Reserved paths that cannot be used:

• api, admin, auth, f, e
• _next, favicon.ico, robots.txt
• And other system-reserved paths