WPForms hosting where every submission reaches the database.
A form that silently fails is worse than a form that errors. The visitor believes they contacted you, and the only evidence is an enquiry that never arrives.
Everything a form plugin needs from a host.
Forms are the one part of a marketing site where a failure produces no error and no log entry - just silence.
Submissions that are never served from cache
The AJAX endpoint a submission posts to has to reach PHP every time. Cached even briefly, it returns somebody else's success message and the entry is never written.
Upload limits set to what you accept
A form advertising 25 MB attachments on a host capped at 8 MB fails at the moment the visitor is most invested. The limit is set to match the form, not the default.
An entries table that stays queryable
Entries, entry meta and entry fields grow together. A busy form makes the entries screen the slowest admin page on the site within a year.
Notification mail that leaves the building
Form notifications sent through PHP mail are the most commonly silently dropped mail on WordPress. Authenticated delivery and a log means you can prove it sent.
Spam filtered before it is stored
Every spam submission is a write, a notification and a row. Filtering at the edge keeps the cost off the database rather than cleaning up afterwards.
Prove the enquiry arrived.
When somebody says they filled in the form last week, you want an answer better than checking whether it looks like it works.
- Delivery log for every notification
- Alert on submission errors
- Entry retention set and enforced
- Restore any daily backup from the dashboard
A form on a page that gets shared.
The page caches beautifully. The submission behind it cannot, which is the part that decides whether the campaign produced anything.
What we change for WPForms
These differ from a standard WordPress site on the same plan, and each follows from a form being the one uncacheable thing on an otherwise static page.
| Setting | What we do | Why |
|---|---|---|
| Submission endpoints | Excluded from the page cache without exception | A cached form response returns a stored success message to a visitor whose data was never written, which produces a happy visitor and no enquiry. |
| Upload size limits | Raised to match the largest attachment the form advertises | A form offering a file size the server rejects fails at the final step, after the visitor has already filled in everything else. |
| Entries tables | Indexed, with a retention policy applied | Entries, meta and fields grow as three joined tables, so the admin listing degrades long before anybody thinks of the form as high volume. |
| Notification delivery | Authenticated SMTP with a per-message log | Form notifications sent through PHP mail are dropped by recipient providers without a bounce, so nothing on either side records that the message existed. |
| Spam handling | Filtered at the edge before a row is written | Every spam submission otherwise costs a database write, a notification attempt and a row somebody has to delete later. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why do some WPForms submissions never arrive?
Can I accept large file uploads through a form?
My entries screen has become very slow. Why?
Does caching break conditional logic in forms?
How long are form entries kept?
Run WPForms on a host where submissions cannot silently fail.
Free migration, endpoints exempt from cache, and a delivery log that proves the notification sent.