Cognito Forms Custom Domains: Not Supported—What Works Instead [2026]

Quick answer: No. Cognito Forms doesn’t support custom domains—there’s no native feature for serving forms from your own web address. Per Cognito’s own documentation: “You cannot use a completely custom top-level domain directly for Cognito Forms URLs.” Every form lives on a three-part Cognito URL—www.cognitoforms.com/YourOrganization/FormName—and what Cognito offers instead is customization of the parts around the edges: the form name at the end of the path (editable per form), and embedding the form onto your own website, which is Cognito’s documented recommendation for making a form “display under your own website domain.” Each is partial, and neither puts the form itself on your domain.

In this guide, we’ll break down how Cognito’s URL structure works, what each customization actually gets you, where the honest limits sit—and what your options are if the form’s address should carry your brand.

No. Cognito forms are hosted on Cognito’s infrastructure at Cognito’s web addresses. There’s no custom domain setting, no documented add-on, and no DNS-based path to serving a form from surveys.yourbrand.com.

Understanding what is customizable starts with the structure. Every public Cognito form URL has three layers:

https://www.cognitoforms.com/YourOrganization/FormName
                                 ───────┬────────  ────┬───
                            fixed org path    editable form name

Here’s the landscape of options, at a glance:

The pattern to hold onto: you can tidy the end of the path and you can wrap the form in a page you own—but the domain layer never changes. On every shareable link, in every address bar, cognitoforms.com is the registrable address.

The one natively editable piece is the form name. Per Cognito’s documentation, in your form settings you can edit the specific portion of the public URL that appears after https://www.cognitoforms.com/YourOrganization/—making it shorter or more relevant.

That’s genuinely useful: a link ending in /membership-application beats a random string, and it makes links easier to read, type, and share. Combined with the organization path, Cognito URLs are more human-readable out of the box than platforms that expose raw IDs.

What it doesn’t change is everything to the left of the form name. The result is still cognitoforms.com/YourOrganization/FormName—your brand appears only in the folder you’re stored in, on a domain you don’t own. And the structure means the shortest possible Cognito URL is still two path segments deep under someone else’s domain—there’s no equivalent of a root-level yourbrand.com/contact.

The second option is Cognito’s own recommended route. Per their documentation: “To make a form display under your own website domain, Cognito Forms recommends using their embedding guides to place the form directly onto platforms like Wix, Weebly, or Squarespace.”

The mechanics: create a page on your website—where the URL is yours, like example.com/contact—and place the Cognito form inside it via embed code. Cognito publishes embedding guides for the major website platforms, so if your site runs on one of them, the setup is documented.

The honest limitation: embedding changes who owns the page, not the form. The form itself is still hosted and served by Cognito’s infrastructure, and it renders with its own appearance inside your carefully branded page—styling, layout, and submission flow included. A few practical consequences follow from that:

• The branded URL belongs to the page, not the form. What you share is the page’s address. The form has no independent branded address of its own—remove the page, and the branded URL is gone.
• The look has to be reconciled. An embedded Cognito form sits inside your page with its own styling, which can read as a third-party widget rather than part of your site unless you invest in matching them.
• You’ve added a dependency. The form inside your page loads from Cognito’s servers—your page’s most important element depends on a third party’s uptime and load behavior.
• It doesn’t help links that skip your site. Sharing, QR codes, ads, and email signatures that point at the form directly still land on cognitoforms.com unless you route everything through your embed page first.

If your form was always going to live inside a website page, embedding is a normal pattern and Cognito’s guides make it accessible. Just be clear about what it is: your page around their form—not the form living on your domain.

There’s no price to look up, because there’s no feature to price. Cognito’s documentation doesn’t present custom domains as a plan feature at all—there’s no documented tier, add-on, or upgrade that adds them. The branded-URL question on Cognito Forms is answered with the two options above: an editable form name (included, on Cognito’s domain) and embedding (included, on your page).

That makes Cognito’s case different from platforms where custom domains exist behind a sales contract or a paid add-on. Here, the gap isn’t a paywall—it’s a product boundary. No amount of spend moves a Cognito form onto a domain you own.

• No native custom domains. Cognito’s documentation states it directly: you cannot use a completely custom domain directly for Cognito Forms URLs. The domain layer is fixed.
• The org path is baked in. Every URL carries the /YourOrganization/ segment—your account’s folder on Cognito’s domain. There’s no root-level, single-segment URL option.
• Editable form names stop at the path’s end. You can shorten and clarify the slug, but the domain and org path remain in every link.
• The custom-domain route is embedding. That’s Cognito’s documented recommendation—with the page-vs-form ownership limits described above.
• Direct links can’t be branded. Any link that points at the form itself lands on cognitoforms.com; only your embed page’s URL is yours.

What works well: the editable form name makes Cognito’s URLs genuinely readable—more so than raw-ID links on many platforms—and the embedding route is documented with platform-specific guides rather than left to guesswork. For forms that live inside a website page as part of a broader site experience, embedding is a workable pattern. The ceiling only shows when the form’s own address—the one in QR codes, ads, signatures, and the address bar—needs to be yours.

Both Cognito options share the same ceiling: the form itself never leaves cognitoforms.com. Here’s the direct comparison:

Real hosting vs. a page around a form. Embedding puts a Cognito form inside your page—the page is yours, the form is Cognito’s. Formware hosts the form itself on your domain: the visitor stays on ask.acme.com/contact through every question and the thank-you page, with the address bar showing your brand the entire time. And when you do want the form inside a page, Formware embeds into WordPress, Webflow, Framer, Shopify, Wix, Squarespace, Carrd, Weebly, and custom-coded sites—fully styled to match, with the badge removed on Pro rather than visibly third-party.

Included at a published price vs. a product boundary. Formware’s custom domains sit on Pro at $29.99/month or $299/year—the same published price for everyone, with SSL provisioning and renewals handled automatically. On Cognito Forms, the capability isn’t a tier to buy—it’s a boundary, with URL tidying and embedding as the documented substitutes.

Clean URLs vs. the three-part path. Formware maps each published form to a path you assign—ask.acme.com/contact, ask.acme.com/customer-survey—with no organization folder and no fixed domain. For QR codes (or QR codes generated straight from your form), print materials, ad campaigns, and email signatures, a link people can read and type—and that says your brand—beats a path nested under someone else’s domain.

Branding beyond the URL. On Formware Pro, the domain comes bundled with white-labeling—no “Powered by Formware” badge, your logo and favicon—plus per-ending custom redirects that hand respondents off to a booking page or checkout, respondent email notifications, and WhatsApp capabilities (sharing, widgets, and forwarding responses) if WhatsApp is a lead channel for your business.

The free-plan math. Formware’s free plan offers unlimited forms, questions, and responses (subject to fair use), alongside hidden fields (pair them with the UTM builder for campaign tracking), recall, and conditional logic at no cost. Pro is the single step up, and it exists for exactly the layer Cognito’s URL structure can’t reach: putting the form—URL, styling, and all—under your brand.

If you’re weighing Formware against Cognito Forms more broadly—beyond just domains—we break down the full comparison in Formware vs. Cognito Forms.

No. Cognito Forms doesn’t offer a native custom domain feature—its documentation states that you cannot use a completely custom domain directly for Cognito Forms URLs. Forms are hosted on cognitoforms.com with a three-part structure: domain, organization path, and form name. The documented alternatives are customizing the form name and embedding the form on your own website.

No. There’s no documented mechanism for pointing a domain or subdomain at Cognito Forms, and DNS records alone can’t make Cognito serve your form from your hostname. The documented route to a form under your own web address is embedding it on your site—and even then, the form is still hosted and served by Cognito.

Partially. In your form settings, you can edit the form name—the portion of the public URL that appears after https://www.cognitoforms.com/YourOrganization/—to make it shorter or more relevant. The domain and the organization path are fixed. So cognitoforms.com/YourOrganization/Membership-Application is achievable; forms.yourbrand.com/contact is not.

It’s Cognito’s documented recommendation for making a form display under your own domain, but it’s not a custom domain in the usual sense. The visitor’s address bar shows your page’s URL, but the form itself is hosted by Cognito, keeps its own appearance, and has no independent branded address. It’s your page around their form.

Not natively. There’s no custom domain or subdomain feature in Cognito Forms’ documentation—no DNS setup, no verification flow, no plan tier that adds one. The only way to get a form onto a forms.mybrand.com address is to embed it into a page hosted at that address yourself. Formware supports subdomains natively—CNAME setup, automatic verification, automatic SSL—on its Pro plan.

Custom domains aren’t presented as a plan feature anywhere in Cognito’s documentation—there’s no documented tier, add-on, or upgrade that includes them. The branded-URL options are the same at every level: an editable form name and embedding. Formware includes custom domains on Pro at $29.99/month or $299/year, published on its pricing page.

No. Cognito’s URL structure always includes the cognitoforms.com domain and your organization path, with the editable form name at the end. Root-level, single-segment URLs on your own domain aren’t supported. Formware maps each published form to a path like ask.acme.com/contact on its Pro plan.

Formware includes custom domains on Pro at $29.99/month or $299/year—published pricing, self-serve DNS setup with automatic verification, both apex domains and subdomains, automatic SSL issuance and renewal, and clean per-form URLs like ask.acme.com/contact. It also embeds into WordPress, Webflow, Framer, Shopify, Wix, Squarespace, and Weebly when you want a form inside a page—with white-labeling included. Its free plan offers unlimited forms, questions, and responses, plus hidden fields, logic, and recall. See the full Formware vs. Cognito Forms comparison.

Cognito Forms’ URL customization and embedding options were verified at the time of writing and may change. Check Cognito’s documentation for current details.