A form-driven site accumulates its problems quietly. Entries pile up, uploads pile up, and the admin screen you use to read them gets slower every month.
Nothing here is about rendering a form. It is about the year of data that arrives through it.
Every submission is rows in the entry and meta tables, and the admin list view queries across all of them. Those lookups are indexed so reading last week's entries does not get slower every month.
Attachments submitted through a form are stored behind access checks rather than in a browsable uploads path, because people submit passports and invoices through forms without thinking about it.
A submission can trigger several notifications and a handful of webhooks. Those run with limits that let the chain complete rather than timing out after the first two.
Public forms attract automated submissions constantly. That write volume is absorbed by your plan's limits rather than filling the entries table faster than anyone can moderate it.
Submissions are business records, often the only copy. They are in the daily backup along with the uploads attached to them.
Form plugins are judged on the front end and lived with on the back end. The entry list is where a form-heavy site actually becomes unpleasant to use.
The number that matters is how long the entry list takes to load in year two, not how fast the form renders on day one.
A form plugin's cost is not the form. It is the table behind it, which grows every day and is never cleaned up.
| Setting | What we do | Why |
|---|---|---|
| Entry table indexing | Indexed on form, date and status | The admin entry list filters on exactly those three, and unindexed it scans a table that grows with every submission. |
| Form attachments | Stored behind access checks | People submit identity documents and invoices through forms, and a guessable uploads URL exposes them to anyone. |
| Notification chains | Given execution room beyond a normal request | One submission can fire several emails and webhooks in sequence, and a default timeout truncates the chain silently. |
| Export runs | Own memory and execution ceilings | Exporting a quarter of submissions is a batch job that a page request's limits would kill part way through. |
| Spam volume | Absorbed within plan limits rather than blocking writes | Public forms receive automated submissions continuously, and that write load is constant rather than occasional. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the site across — migration is free, entries and attachments included.