Built for site owners who need the form live by Friday
A free contact form for your website that installs with one line of code.
The ask is small: a working contact form on an existing website. The gap is usually the stack. WordPress plugins add bloat. Squarespace native forms stop at email. Wix free forms route into a Wix inbox nobody checks. Strkr's embed drops onto any site with a one-line script tag, with submissions landing on a real CRM record. No credit card.
Teams searching for a free contact form for a website are usually constrained in a way: the site exists, the hosting is set, and adding a new tool means fighting a plugin ecosystem (WordPress), a native-form product (Squarespace, Wix), or a developer backlog (custom HTML, headless CMS). The pain below is what site owners run into when they try to add a form that behaves like a lead-capture system rather than a one-way email dispatcher.
Plugin bloat on WordPress
Contact form plugins pull in a dozen other dependencies.
A popular WordPress form plugin can add 400 KB of JavaScript on every page load, require 3 to 5 other plugins for features that should be standard, and slow the site to a crawl. Strkr's embed is a 12 KB script that loads on the pages where the form appears, with no plugin tree to maintain.
Native forms that go nowhere
Squarespace and Wix forms end at a hosted inbox.
Squarespace Forms deliver to the owner email and store the submission inside Squarespace with no CRM concept. Wix free forms route into the Wix Inbox with the same limitation. Teams want a real customer record with an owner and a follow-up discipline. Strkr delivers that on top of the same embed-first install.
Shopify contact app bills
The free Shopify form apps upcharge for routing.
Shopify contact-form apps often ship free with basic submission but charge $5 to $20 monthly for routing, custom fields, or spam defense. Strkr's Starter embed on Shopify ships routing, custom fields, UTM capture, and spam defense at zero cost.
No Webflow-friendly options
Webflow native forms require a paid site plan for 10 submissions.
Webflow's native forms cap at 50 submissions per month on the Basic site plan and require Business ($39 per month) for 500 submissions. Strkr's embed on Webflow works regardless of site plan tier, with no per-site-month cap on the Starter plan.
Static-site friction
Jamstack sites usually route forms through a form-handler service.
Static sites (Jekyll, Hugo, Astro, Next.js static exports) typically need a form-handler service (Netlify Forms, Formspree, Basin) with its own per-month submission cap and no CRM. Strkr's embed drops onto the static site directly with the same CRM behind it as the dynamic-site install.
Mobile responsiveness
Embedded iframes break on narrow screens.
Many free form widgets ship as iframes that have fixed dimensions and overflow on mobile viewports. Strkr's embed is responsive by default and adapts to the container width, so the form on a 375-pixel phone looks the same as the form on a 1440-pixel desktop.
The install step for each CMS
One-line embed that works on every common website platform.
The Strkr embed is a 12 KB script with a one-line installation. The platform-specific details below cover the exact step for each common website host.
WordPress
Paste the embed into a Custom HTML block.
Open the page or post in the WordPress editor, add a Custom HTML block, paste the Strkr embed snippet. The form appears inline on the page. No plugin install, no plugin update maintenance, no plugin conflict. Works on both WordPress.com (with HTML-block access) and self-hosted WordPress.org.
Squarespace
Code block in the Squarespace editor.
In the Squarespace page editor, add a Code block (available on Business plan and above), paste the embed snippet. The form renders inline with the Squarespace page styles inherited. For Personal plans without Code blocks, the embed goes in the Code Injection section of site settings for a sitewide form.
Wix
HTML embed element in the Wix editor.
In the Wix editor, add an HTML Embed element (under Add Elements), paste the Strkr snippet. The form renders inline. Wix Studio supports the same embed through the Dev Mode HTML component. The Strkr embed replaces the Wix native form and ships a CRM behind it.
Webflow
HTML embed component in the Webflow Designer.
In the Webflow Designer, add an HTML Embed component, paste the Strkr snippet. The form renders in Designer preview and on the published site. The embed bypasses Webflow's native form submission caps because the submission goes to Strkr rather than to the Webflow form handler.
Shopify
Custom Liquid section or theme code.
In the Shopify theme editor, add a Custom Liquid section with the Strkr embed. The form appears on the page where the section is placed. For stores that want the form in the theme-wide footer or header, the snippet goes in the theme code editor directly on the theme.liquid file. Works on all Shopify plan tiers.
Framer
Embed component in the Framer canvas.
In the Framer canvas, drag an Embed component onto the frame, paste the Strkr snippet. The form renders in Framer preview and on the published site. The embed works with Framer's responsive breakpoint system because the Strkr form is container-width responsive.
Static sites
Paste into the HTML template or markdown file.
For Jekyll, Hugo, Astro, Next.js, Gatsby, Eleventy, and other static-site generators, the embed snippet pastes into the HTML template, layout, or markdown shortcode. The script tag loads at render time; the form renders without server-side processing. Static-site form-handler services (Netlify Forms, Formspree) become unnecessary because Strkr handles submission directly.
Raw HTML sites
Paste the snippet into the HTML page.
For hand-coded HTML sites, the embed snippet pastes into the page body where the form should appear. The script loads async, so the surrounding page content is not blocked. The form inherits body font-family and color by default and supports custom CSS for teams that want tighter brand control.
Mobile-friendly by default
The form adapts to the container width.
The Strkr embed is responsive at 375, 768, 1024, and 1440 pixel breakpoints by default. Field widths adjust, labels remain legible, and the submit button scales. For teams that want a mobile layout, custom CSS overrides are supported. The common iframe-overflow failure on narrow phones is designed out.
What the embed actually ships
Six capabilities that make the free website form behave like a system.
The embed itself is a thin surface. The real value is what happens between submit and record. Below is the stack behind the one line of code.
CRM record on submit
The submission becomes a contact with timeline and owner.
Every submit creates a contact record with the form fields mapped onto standard and custom contact properties. The submission payload is logged on the activity timeline with timestamp, IP, and originating URL. The record is a first-class CRM entity, not a side-table entry.
Routing on submit
Round-robin, territory, or field-answer-based assignment.
Strkr assigns an owner at the moment of submission using round-robin for even distribution, territory rules for geography-based routing, or field-answer rules for pattern routing (wholesale to Pat, press to Sam). The record arrives with a name attached rather than entering a shared alias and competing for attention.
Validation that catches typos
Format, length, required, disposable-domain block.
Validation runs client-side at submit and server-side on receive. Email format checks catch gmial.com and other common typos. Length rules protect against paste-dump attacks. Disposable-domain checks block throwaway signups. Submitters see errors inline before the form clears.
Spam defense three-layer
Honeypot plus rate limit plus optional CAPTCHA.
The honeypot is invisible to humans but filled by naive bots. Rate limiting caps submissions per IP per hour. Optional reCAPTCHA layers on for heavier bot traffic. The default stack catches roughly 95 percent of bots without affecting real users.
UTM capture built in
Attribution without the submitter seeing extra fields.
Hidden fields capture utm_source, utm_medium, utm_campaign, utm_content, utm_term, referrer, and landing URL automatically. The record carries attribution without the submitter interacting with those fields. For teams running paid ads or newsletter campaigns, the channel-to-pipeline link becomes visible.
Zero-friction notifications
Email plus optional mobile push within seconds.
The assigned owner gets an email notification with the submission details and a direct link to the record. Teams on the Strkr mobile app receive a push notification. The 5-minute response window that drives inbound conversion is actually hittable because the notification arrives in time to act on.
Where the website-embed approach wins
The install-friendly design cuts the typical form project to under an hour.
Most teams expect installing a free contact form onto a website to take a half-day: pick a tool, test the embed, debug a plugin conflict, wire the notifications. The Strkr pattern collapses that to the time it takes to paste a snippet.
One snippet, every platform
The same code works on WordPress, Squarespace, Wix, Webflow, Shopify.
The embed snippet is identical across every CMS. The platform-specific step is where to paste it (HTML block, code embed element), not what to paste. The pattern eliminates the learn each platform's form system overhead.
No plugin tree
The WordPress install is a 12 KB script, not 400 KB of dependencies.
WordPress sites avoid the plugin-dependency tree that most form plugins pull in: no admin interface in wp-admin, no plugin update cycle, no plugin conflict risk. The script loads on the pages where the form lives.
Bypass native form caps
Webflow and Shopify submission caps do not apply.
Native form systems on Webflow (50-500 per month depending on plan) and Shopify (app-dependent) stop applying because the submission flows to Strkr, not the native handler. The Starter plan does not cap submissions.
Jamstack-friendly
Static sites install without a form-handler service.
Jekyll, Hugo, Astro, Next.js static exports, Gatsby, and Eleventy sites can embed the Strkr form directly without a form-handler service like Netlify Forms or Formspree. The form submits to Strkr's endpoint, which bypasses the per-month submission caps that free-tier handlers impose.
Responsive by default
The form adapts without custom CSS.
Container-width responsive at 375, 768, 1024, 1440 pixel breakpoints. The common failure of iframe-based forms overflowing on narrow phones does not happen because the embed is not an iframe.
Custom CSS when you want it
Brand-level styling without touching the embed script.
For teams that want the form to match brand design pixel-for-pixel, custom CSS applies through the form settings in the Strkr admin. The embed script stays the same; the styling layers on. No code changes on the website side.
Head-to-head
Strkr embed vs CMS-native forms and plugin-based options.
The common free-form-for-website options each ship with a tradeoff. the comparison below covers the capabilities that matter for a site owner who wants the form working by Friday.
Feature
Strkr
Squarespace / Wix / Webflow / WPForms Lite
Install step
One-line script tag
Platform-specific form builder or plugin
CRM record on submit
Full CRM contact with timeline
Hosted inbox or spreadsheet typical
Submission cap
No cap on Starter
Webflow Basic: 50/mo; Shopify: app-dependent
Owner assignment
Round-robin, territory, field-based
Manual triage from shared alias
Validation
Format + length + disposable-domain
HTML5 basic typical
Spam defense
Honeypot + rate limit + optional CAPTCHA
Varies, often minimal
UTM capture
Automatic on hidden fields
Paid upgrade typical
Mobile responsiveness
Container-width responsive
Iframe overflow common
Custom CSS
Via admin, no code changes
Platform-specific overrides
Credit card at signup
No
Varies
How teams use Strkr
How site owners install a Strkr contact form today.
The playbooks below are patterns site owners run when embedding the free contact form onto a working website. Each is a direct install story rather than a theoretical setup.
Agency owner, WordPress site
Replaced Contact Form 7 in 20 minutes.
A brand agency ran Contact Form 7 on a self-hosted WordPress site, delivering to a shared inbox with a spam-filter miss rate running roughly 1 in 15 submissions lost. The owner replaced the plugin with a Strkr embed in a Custom HTML block on three pages (contact, work, home). Total install time was under 25 minutes. The CF7 plugin was deactivated. Inbox losses dropped to zero because submissions landed on records. The owner reported the WordPress admin dashboard loading noticeably faster after removing the plugin dependency tree.
Squarespace boutique store
Code block instead of native form, instant notifications.
A Squarespace store on the Business plan replaced the native contact form with a Strkr embed in a Code block. The native-form delivery had been going to a Gmail inbox with roughly 2 to 4 missed inquiries per week during busy periods. The Strkr embed delivered submissions to a CRM record with mobile push notifications. The owner reported Thursday and Friday response times dropping from a typical 2 to 6 hours to under 20 minutes.
Webflow freelance consultant
Bypass the 50-submission cap on the Basic site plan.
A solo consultant ran a Webflow Basic site that capped at 50 form submissions per month through the native Webflow form handler. Monthly inbound was averaging 65 to 80 inquiries, meaning the cap was triggering upgrade prompts to Webflow Business at $39 per month. The consultant installed a Strkr embed in a Webflow HTML Embed component, bypassed the native cap entirely, and kept the Basic site plan. The pattern saved roughly $468 per year on the Webflow upgrade alone.
Astro static blog
Static-site contact form without Formspree or Netlify Forms.
A technical consultant running an Astro-based static blog on Cloudflare Pages needed a working contact form without introducing a form-handler service. Formspree free tier caps at 50 submissions per month; Netlify Forms free tier caps at 100 per site per month. The consultant installed the Strkr embed in the Astro layout file, which rendered on every page. Submissions flowed directly to Strkr with no form-handler intermediary. Submission volume ran roughly 110 per month over the first quarter; no cap-related upgrade conversation occurred.
Shopify brand owner
Wholesale-inquiry form in the Shopify theme without a paid app.
A Shopify-based coffee roaster added a wholesale-inquiry form to the Shopify theme using the Strkr embed in a Custom Liquid section. The alternatives in the Shopify App Store cost $10 to $25 per month for comparable routing and CRM capability. The brand owner saved roughly $240 per year on the app subscription while getting a routing-plus-CRM pattern that the native Shopify Forms option could not deliver.
A free contact form that drops onto your existing website today.
Grab the embed snippet, paste it into your WordPress HTML block or Squarespace Code block or Webflow Embed component. Submissions land on CRM records with an owner and a notification. No credit card.
The Strkr embed script is 12 KB gzipped and loads async, which means the surrounding page content is not blocked while the script loads. On a representative WordPress site with Core Web Vitals targets, the embed adds roughly 20 to 40 milliseconds to Largest Contentful Paint, which is below the perceptual threshold for most pages. The common WordPress alternative (a popular form plugin pulling in jQuery dependencies plus admin assets on every page) typically adds 200 to 400 KB and 100 to 200 milliseconds. The embed is designed to be the lighter option.
Does the embed work on free-tier CMS plans like Squarespace Personal or Wix Free?
The embed requires the ability to insert HTML or a code block on the page. Squarespace Personal plan does not include Code blocks, so the embed on Personal plan requires using the Code Injection area in site settings (sitewide) rather than a per-page block. Squarespace Business plan and above support Code blocks for per-page embedding. Wix Free plan supports HTML Embed elements. Wix Studio supports the Dev Mode HTML component. For CMS tiers that genuinely do not allow any code insertion, the Strkr-hosted form (a shareable form URL with no embed required) is the alternative path.
Can I style the form to match my brand without touching the embed script?
Yes. The embed snippet itself is unchanged across styling. Custom CSS applies through the form settings in the Strkr admin UI, with support for fonts, colors, border radius, button styling, field spacing, label positioning, and dark-mode variants. The CSS lives server-side and loads with the form, so the website owner does not touch the website code to adjust styling. For teams with specific brand constraints (minimum font sizes for accessibility, color contrast ratios), the admin surfaces an accessibility check that flags WCAG AA failures before publish.
What happens if my CMS or site platform is not on the supported list?
The embed is a plain HTML script tag plus a form container div. Any CMS or static-site generator or hand-coded HTML that supports pasting raw HTML into the page body supports the Strkr embed. The platform-specific instructions in the admin UI cover the common systems, but the underlying mechanism is standards-based and works wherever HTML works. For teams on obscure or custom-built CMS platforms, the admin UI offers a Strkr-hosted form (a shareable URL) as an alternative that requires no embed at all; the owner shares the URL from the main site and submissions flow to the same CRM.
How does the Strkr embed handle mobile viewports?
The embed is responsive by default at 375, 768, 1024, and 1440 pixel breakpoints with container-width adaptation. Field widths flex to fit the container. Labels remain legible on narrow screens. The submit button scales. Textarea heights adjust. The common iframe-based form failure (fixed-width iframe overflowing a 375-pixel phone viewport) does not occur because the embed is not an iframe; it is DOM-level HTML inside the host page. For teams testing on real devices, the admin preview UI simulates the four standard breakpoints to validate the layout before publish.
What if I want to switch away from Strkr later; is the data portable?
Yes. Full data export is a baseline on every plan including Starter. Admins trigger exports from the admin UI at any time. The export includes contact records, companies, custom fields, notes, tasks, activity timeline (submissions, email, call logs), and attached files in CSV plus JSON plus attachment archive format. The export maps cleanly to common CRM imports (HubSpot, Salesforce, Zoho, Pipedrive) so a migration back out is a self-serve process rather than a billable extraction service. The posture is that data portability stays available across every tier rather than becoming a procurement concession.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
