Formstack Custom Domains: Plans, Costs & Limitations [2026]

Quick answer: Partially. Formstack offers two tiers of URL branding, and the gap between them is where custom domains live. Self-serve, every account can set a URL prefix—changing form links from formstack.com/… to yourbrand.formstack.com/…. That’s a real branding improvement, but the domain is still Formstack’s. For a fully custom domain (like forms.example.com), Formstack’s documentation describes two routes: embedding the form onto your own website, or contacting your sales representative to enable custom domain features on your account. Neither is available through self-serve DNS setup, and no published plan—including Forms at $83/month—lists custom domains among its features.

In this guide, we’ll walk through what the URL prefix actually gets you, how each documented path to a custom domain works, what the pricing picture looks like, and the limitations worth knowing—plus what your options are if a branded URL is the goal.

Sort of—and the documentation splits the answer in two. Formstack’s help content separates “User-Friendly URLs” (the self-serve subdomain) from “Custom Domains” (embedding or sales enablement). Here’s the landscape:

The distinction that matters: a URL prefix is not a custom domain. It changes the subdomain in front of Formstack’s domain—but the registrable address your visitors see is still formstack.com. It’s the same category of difference as a customized link on any hosted form platform: your brand appears, but the web address belongs to the vendor.

The self-serve option is Formstack’s User-Friendly URLs feature. Per the documentation:

1. Go to My Account and select URLs (only available to account admins).
2. Enter your desired URL prefix.
3. Click Save Settings to update your form links.

Two things to know about how it behaves:

• It applies account-wide. The prefix changes the subdomain for all forms in your account—there’s no per-form choice here. That’s convenient for consistency and restrictive if different forms serve different brands or business units.
• It’s admin-gated. Only account admins can access the URLs setting; other users need an admin to make the change.

The result is links like yourbrand.formstack.com/…—your name in the URL, Formstack’s domain underneath. For internal forms or quick projects, that may be enough. For customer-facing forms where the address itself should carry your brand—ads, print, email signatures, QR codes—it stops short, because formstack.com is still in every link.

The first documented route to a “fully custom domain” is embedding the form onto your own website. The mechanics: you create a page on your own site—where the URL is yours, like example.com/contact—and place the Formstack form inside it via its embed code.

The visitor’s address bar shows your page’s URL, which is why Formstack’s docs present this as the way to “customize the URL.” It’s a genuine option, and if your form already lives inside a website page, embedding is a normal pattern.

The honest limitation: embedding changes who owns the page, not the form. The form itself keeps Formstack’s appearance—its styling, layout, and submission flow—rendered inside your page, and it’s still hosted and served by Formstack’s infrastructure. You’ve put a Formstack form inside a page with your URL, not moved the form onto your domain. That distinction shows up in practice: the embedded form’s look needs to be styled to match your site, the embed adds a dependency on Formstack’s uptime and loading behavior inside your page, and the “form URL” you’re sharing is really the page URL—the form has no independent branded address of its own.

If embedding is your route, the address-bar win is real. Just go in knowing what it is: your page wrapped around their form.

The second documented route is direct: “Custom domains (e.g., forms.example.com) are available for Formstack forms. Please reach out to your Sales representative for more details on enabling this feature.”

That sentence is where Formstack’s public documentation ends—and what’s not published is as informative as what is:

• No published setup flow. Unlike platforms that document the DNS records, verification steps, and propagation expectations, Formstack’s public docs don’t walk through the custom domain setup at all—the mechanics live behind the sales conversation.
• No published pricing. There’s no listed price for the feature, on any plan page—so the cost is part of whatever quote you negotiate.
• No documented DNS or SSL details. Nothing public describes certificate provisioning, renewal handling, or what DNS records are required. Those are questions to put to the sales rep before committing.

For teams that prefer self-serve infrastructure—add a domain, add DNS records, wait for verification—Formstack’s custom domain path starts with a conversation instead.

Formstack’s published lineup:

The pattern should look familiar from the sales-gated tier of this series: custom domains appear on no published plan. The entry point is also worth noting—Formstack’s cheapest plan, Forms, runs $83/month billed annually ($99 monthly), the steepest floor among mainstream form builders. Suite, at $250/month annually, adds document generation, eSignatures, and approval routing—but custom domains aren’t listed there either. Whether the sales-enabled feature carries an additional fee, and how much, isn’t publicly documented.

To be fair to the platform: Formstack’s Forms plan is aimed at a broader workflow product—its Suite tiers bundle document generation, eSignatures, and Salesforce-native forms—and the 300+ integrations list is real. The domain gap isn’t the whole platform story; it’s just the part this page is about.

• No published plan includes custom domains. Forms and Suite don’t list the feature; Salesforce and Enterprise are custom-priced. The feature is enabled through sales, with unpublished mechanics and cost.
• The self-serve ceiling is Formstack’s own domain. The URL prefix puts your brand on formstack.com—useful, but not a web address you own.
• The DIY route is embedding, not hosting. The documented way to put a form at your own URL yourself is embedding it in your page—the page is yours, the form is still Formstack’s, appearance and all.
• URL prefix changes are admin-only and account-wide. Only account admins can set the prefix, and it applies to every form in the account—no per-form or per-brand flexibility.
• No documented DNS, verification, or SSL flow. Formstack’s public docs don’t describe the custom domain setup steps, required records, or certificate handling—confirm all of it with sales before committing.
• Apex domains aren’t part of the documented flow. The documented examples are subdomain-based (forms.example.com); there’s no published process for connecting a bare domain.

What works well: the URL prefix is genuinely self-serve and instant, and it does put your brand into every form link on the account. The embed route is documented and available without any sales contact. And for organizations already buying Formstack for documents, eSignatures, or Salesforce workflows, the domain conversation can ride along with a purchase that’s happening anyway.

The direct comparison, point by point:

Self-serve vs. sales-gated. Formstack’s custom domain starts with a sales representative, with unpublished pricing and no documented setup flow. Formware’s custom domains are a documented, self-serve feature on Pro at $29.99/month or $299/year: add the domain, add the DNS records Formware generates, and the domain moves from Pending Check to Verified as propagation completes—typically minutes to several hours.

Native hosting vs. embed-first. Formstack’s documented DIY route puts the form inside a page you own—the page is yours, the form is still Formstack’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, no embed required. (Formware also embeds into WordPress, Webflow, Framer, Shopify, Squarespace, and custom-coded sites when you want the form inside a page—fully styled and white-labeled rather than visibly third-party.)

Domain types. Formstack’s documented examples are subdomain-based. Formware supports both subdomains via CNAME records and apex domains via A records—acme.com and ask.acme.com both connect.

Clean URLs vs. no documented path structure. Formware maps each published form to a path you assign—ask.acme.com/contact, ask.acme.com/customer-survey—from the domain’s Configure screen, removable with a trash icon. For QR codes (or QR codes generated straight from your form), print, ads, and email signatures, a short readable path beats a link that carries the vendor’s domain at any position in it.

The price floor. Formstack’s cheapest plan is $83/month billed annually, and custom domains aren’t on it—or on any published plan. Formware’s Pro is $29.99/month or $299/year with custom domains included, alongside white-labeling, per-ending custom redirects to booking pages 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—built for exactly the layer Formstack gates behind sales: putting the form—URL, styling, and all—under your brand.

If you’re weighing Formware against Formstack more broadly—beyond just domains—we break down the full comparison in Formware vs. Formstack, or browse our Formstack alternatives guide for the wider market.

Yes, but not self-serve and not on any published plan. Formstack’s documentation states that custom domains (e.g., forms.example.com) are available for Formstack forms when enabled through your Sales representative, and that embedding a form onto your own website is the way to customize the URL yourself. The self-serve option is limited to a URL prefix—yourbrand.formstack.com—which keeps forms on Formstack’s domain.

The URL prefix (Formstack calls these User-Friendly URLs) changes your form links from formstack.com/… to yourbrand.formstack.com/…—your brand appears, but the domain is still Formstack’s, and the change applies account-wide. A custom domain puts forms on a web address you own, like forms.example.com. The prefix is self-serve and admin-only; the custom domain requires embedding or a sales conversation.

Per Formstack’s documentation, there are two routes: embed the form onto your own website (the DIY path to a customized URL), or contact your Sales representative to enable custom domain features on your account. Formstack’s public documentation doesn’t publish the DNS setup, verification steps, or SSL handling for the sales-enabled route—those details come from sales.

There’s no published price. Custom domains aren’t listed as a feature on any published plan—Forms runs $83/month billed annually ($99 monthly) and Suite runs $250/month annually ($299 monthly), with the feature absent from both. Salesforce and Enterprise are custom-priced. The cost of the domain feature itself is part of the sales conversation.

That’s not part of the documented flow. Formstack’s custom domain examples are subdomain-based—forms.example.com—and no public setup process exists for connecting an apex (bare) domain. Formware supports both: apex domains via A records and subdomains via CNAME on its custom domains feature.

Partially—it’s Formstack’s documented way to customize the URL yourself. The visitor’s address bar shows your page’s URL (like example.com/contact), but the form itself is still hosted by Formstack and keeps Formstack’s appearance rendered inside your page. It’s your page around their form, not the form living on your domain. Formware hosts forms natively on your custom domain—no embed required.

That’s not documented in Formstack’s public setup flow. The self-serve option changes the subdomain prefix, the sales-enabled route shows forms.example.com-style examples without published path details, and the DIY route shares your page’s URL rather than giving the form its own branded address. Formware maps each published form to a root-level path like ask.acme.com/contact on its Pro plan.

Account admins only. The URLs setting under My Account is available exclusively to account admins—other users need an admin to create or edit the prefix. And the change applies to all forms in the account at once.

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. Its free plan offers unlimited forms, questions, and responses, plus hidden fields, logic, and recall. See the full Formware vs. Formstack comparison, or our Formstack alternatives guide for the wider market.

Formstack’s URL and plan features were verified at the time of writing and may change. Check Formstack’s site for current plan details before making a purchase decision.