Before you start
These limits apply to both the web console and the mobile app, unless stated otherwise.
This article covers form size, image size, table size, and field count, and how these affect form performance.
Form size
Forms have generous capacity, so you're unlikely to hit a hard limit on overall form size. However, we recommend keeping forms as small and simple as possible — performance and mobile sync can be affected well before any limit is reached.
Follow the guidance below (fields, tables, and images) to keep your forms lean and reliable.
Image size limit
Maximum image size: 20MB per image.
If a single image goes over 20MB, the form will not submit on web.
💡 Tip: The mobile app automatically compresses images over 1MB to help you stay within the limit. The web console does not compress images, so we recommend keeping individual images under 10MB when uploading from the web.
Keep tables within safe row limits
Tables are useful, but they store more data behind the scenes than they appear to. Every cell in a table is a separate stored element — a table with 100 rows and 5 columns creates 500 elements.
Large tables can cause:
Slower loading and saving times, especially with images or complex field types.
Data conflicts if more than one person edits the same form at the same time, which can lead to duplicate rows, shuffled data, or lost entries.
Forms growing large enough to affect performance and mobile sync, especially if the table includes images or attachments.
💡 Recommended: Keep tables under 75–100 rows, using simple text fields where possible. Avoid using tables for large volumes of data or for forms that multiple people will edit at the same time.
Keep the number of fields manageable
There is no strict cap on the number of fields in a form, but performance depends on how many fields it has and how complex they are:
Simple fields (text, dropdowns, dates): forms perform well with up to 250–300 fields.
Complex fields (calculations, conditional logic, conditional visibility): we recommend staying under 30 fields to keep the form running smoothly.
These aren't hard limits, but going beyond them increases the risk of slow loading, syncing issues, or errors — particularly for mobile users syncing forms in the field.
Choose the right form type
Use singleton forms for one-time entries.
Use non-singleton forms for repeatable entries, such as visits or inspections.
For forms that need to show a history over time — for example, risk assessments or support plans — use non-singleton forms. You can copy the previous form and update it, so earlier versions are kept for audits and inspections.
Avoid editing conflicts
Avoid having multiple users edit the same form at the same time. This can cause data conflicts, especially in forms with tables, and may result in lost or duplicated information.
Summary: designing forms that perform well
Keep individual images under 20MB (ideally under 10MB on web).
Keep tables under 75–100 rows.
Keep complex forms under 30 fields; simple forms can go up to 250–300 fields.
Use singleton forms for one-off entries, and non-singleton forms for repeatable or historical records.
Avoid simultaneous editing of the same form.
Design smaller, simpler forms to keep performance and mobile sync fast and reliable.
Related articles
Sections — how singleton and non-singleton forms work
Create a form — includes the Table and Photo field types referenced above
Form submission troubleshooting guide — what to do if a form won't save or submit