Build forms that look exactly like your website.

Match the look of your site

Three steps from a public page to a form that shares your brand.

1. Step 1

   Give the agent your site

   Drop a public HTTPS link in the assistant. Ask it to match the theme. The agent fetches the page and reads brand colors, fonts, and logo.

2. Step 2

   Review the generated CSS

   The agent writes a stylesheet for the form. You can edit the CSS, pick a designer palette, or set colors without writing rules.

3. Step 3

   Publish on your page

   Share a hosted link or paste the web component embed. The same theme applies in both places. You can change the form later without editing the snippet.

Theme tools that stay in this product

Use a site link, a palette, or a CSS box. Hosted and embed forms share the same sheet.

• Colors and type from your site

  The agent can pull theme color, heading fonts, and a logo from a public page. You then keep or change those values in Settings.

• Palettes without CSS

  Pick Midnight or one of twenty designer palettes. Set page, text, button, and button text colors. Custom CSS still wins if you add it.

• A real CSS box when you need it

  50,000 character cap. Unsafe CSS is stripped. Target .rf-form-root variables and .rf-* classes. The same sheet styles the hosted page and the embed.

• Logo and corners

  Add a logo, set corner radius, and keep buttons in your brand shape. The live preview shows the theme while you build.

Embed without a visual break

The form should read as part of your page, not as a borrowed box.

• The form keeps its own look

  The embed is a web component with a shadow root. CSS on the host page does not restyle the fields. The form CSS does. That keeps your brand, not the host theme by accident.

• Inline or modal

  Web component embed: inline, button modal, link modal, and RequestForms.open. Free.

• No snippet churn

  Paste the snippet once. Edit questions, logic, and CSS in Request Forms. The embed loads the latest published form.

Keep the chrome off the form

Theme matching is free. Hide the vendor link or serve the form on your host when you upgrade.

• Hide the vendor link

  Hide the Request Forms link on a paid organization. Free forms keep the link.

• Serve forms on your host

  CNAME a hostname and serve forms on that host. Needs a paid organization.

Where a matching form matters

Use this when the form sits next to your own design, not in a generic inbox.

• Contact on a marketing site

  Put a contact form in the same colors and type as the rest of the page. Visitors stay in your brand from the hero to submit.

• Careers on the company site

  A job form that looks like the careers page reads as part of the company, not a borrowed tool.

• Client intake next to case studies

  Match the studio or agency site so the intake form feels like the work, not a generic widget.

• RSVP on a campaign page

  Event colors, fonts, and buttons stay consistent from the landing block to the confirmation screen.

Guides

Read the CSS and embed docs, or return to the AI builder on the home page.

• Custom CSS docs
• Embed docs
• Pricing
• AI form builder home

Questions

How does the form match my website?

Open the assistant and paste a public HTTPS page. Ask it to match the theme. The agent reads colors, fonts, and logo, then writes custom CSS. You can also pick a palette or edit the CSS yourself.

Does the embed pick up CSS from my website?

No. The embed runs in a shadow root, so host styles do not restyle the fields. Style the form in Request Forms. Then the embed and the hosted page share that look.

Can I hide Request Forms branding?

Hide the Request Forms link on a paid organization. Free forms keep the link.

Do I need to write CSS?

No. Pick a theme or let the agent write the sheet from a site link or a screenshot. Open the CSS box only when you want a precise rule.

Does a custom domain change the look?

The theme stays the same. A paid organization can CNAME a hostname and serve the form on that host. Search engines then see your domain as the form URL.