ChargeForms

Yes. Every feature included in this WordPress.org plugin is available without a paid license, time limit, or submission cap.

No. Everything is drag-and-drop — fields, conditional logic, multi-step layout, and payment setup are all configured from the builder UI, no code required.

No. The front end only loads the JS/CSS a given form actually uses, not an admin-sized bundle — visitors never download builder code they'll never run.

Yes. Show or hide any field based on other answers, with nested AND/OR/NOT groups for more complex rules.

Yes. Multi-step forms come with a progress bar and per-step validation built in.

Yes. Every entry can be filtered, exported, and managed from the wp-admin entries dashboard, and CSV entry import is included free.

Yes. The built-in Migrator (Tools screen) reads your existing forms directly from each plugin's own data and rebuilds them as ChargeForms forms.

Please use the support forum — that's actively monitored.

The assets/build/ files shipped in this plugin (builder.js, frontend.js, and their CSS) are compiled by webpack from real, unminified source — nothing here is obfuscated, only minified for production the same way every WordPress admin ships its own JS. That source ships in this same plugin package: see assets/src/ for the real, readable JavaScript, and webpack.config.js/webpack.vue.config.js plus package.json for the exact build configuration and tooling versions used to produce assets/build/ from it. To rebuild it yourself: npm ci followed by npm run build (the admin builder and public front-end bundle) and npm run vue:build (the Vue-based Forms List screen).

Google Fonts (optional, off by default). Turned on under Global Settings > General, this plugin loads the Poppins typeface from Google Fonts (fonts.googleapis.com/fonts.gstatic.com) on ChargeForms' own wp-admin screens only (never on your site's front end, never on a visitor-facing page) so the admin UI matches its own design. No request to Google happens until you enable it; the admin UI uses your system font stack otherwise. While enabled, this sends the logged-in admin's IP address and browser info to Google on every admin page load, the same as any page that embeds a Google Fonts stylesheet. Google's terms: https://developers.google.com/fonts/faq and privacy policy: https://policies.google.com/privacy. reCAPTCHA / hCaptcha / Cloudflare Turnstile / CleanTalk. Entirely optional, off by default. If you turn one on (Global Settings > Security) to add spam protection to your forms, the corresponding third-party service's own script loads on your front-end forms and processes the visitor's IP/browser data per that service's own terms — Google (reCAPTCHA): https://policies.google.com/privacy, hCaptcha: https://www.hcaptcha.com/privacy, Cloudflare (Turnstile): https://www.cloudflare.com/privacypolicy/, CleanTalk: https://cleantalk.org/privacy. Stripe / PayPal (optional). Only active on a form where you've added a Payment field and connected your own Stripe or PayPal account (Global Settings > Payment Settings). When a visitor pays, the payment amount and the payer's billing details they entered are sent directly to Stripe (https://stripe.com/privacy) or PayPal (https://www.paypal.com/privacy) to process the charge — standard for any WordPress payment plugin. Nothing is sent to either service on a form with no Payment field. Your own configured integrations (Webhook, Mailchimp, Slack, Discord, Telegram, Notion, HubSpot, Google Sheets). Only ever send data if you explicitly connect them yourself (Integrations screen) — nothing is sent to any of these unless you've entered your own API key/URL for that specific service. When connected, every submission's data is sent to that service at the time of submission: Mailchimp (subscriber added to your list) — https://mailchimp.com/legal/terms/ / https://mailchimp.com/legal/privacy/; Notion (a page created in your database) — https://notion.notion.site/Terms-and-Privacy-28ffdd083dc3473e9c2da6ec011b58ac / https://www.notion.com/trust/privacy-policy; HubSpot (a contact created/updated in your CRM) — https://legal.hubspot.com/terms-of-service / https://legal.hubspot.com/privacy-policy; Telegram (a message sent via your bot) — https://telegram.org/tos / https://telegram.org/privacy. Address autocomplete (optional). If a form uses the Address field's autocomplete feature, each keystroke in the address box is sent to OpenStreetMap's Nominatim search API (nominatim.openstreetmap.org) to fetch matching addresses. Nominatim usage policy: https://operations.osmfoundation.org/policies/nominatim/ — OSM Foundation privacy policy: https://wiki.osmfoundation.org/wiki/Privacy_Policy. License validation (Pro only). If you activate a Pro license key, that key and your site URL are sent to chargeforms.com to verify it. Nothing is sent if you're on the free plan. Terms: https://chargeforms.com/legal/terms — Privacy: https://chargeforms.com/legal/privacy.