No plot limits, no plot fees
Buildsnapper's pricing is flat: one subscription, one device, everything on it. There is no per-plot charge, no per-project charge, and no tier that unlocks "more plots". A forty-plot site costs the same as a single self-build. This is deliberate — some competing products charge per plot lodged, which quietly turns a large site into a large bill.
Within the app:
- Projects: unlimited. Each needs a unique name (the app enforces this so reports can never be attributed to the wrong project).
- Plots per project: no fixed count. Add plots from the project's edit screen as the site grows.
- Photos per plot: no fixed count per section — take as many as the evidence needs.
The real-world constraints, honestly
Two practical ceilings exist, and both announce themselves before causing trouble:
- Phone storage. Each photo's in-app working copy is deliberately compact (about a quarter of a megabyte to half a megabyte typically), so even a busy season's evidence uses modest space. The bigger consumer is the full-resolution gallery backups, which your phone manages like any other camera photos. You can check the app's own footprint under Settings → App Data in the app.
- Per-project record size. Each project's online record (plot lists and photo details — not the images) has a generous ceiling. Only very large single projects approach it, and the app warns you explicitly and early — see the project storage limit article. On big sites, splitting phases into separate projects sidesteps it entirely.
Organising large sites — what works
- One project per site or phase, one plot per dwelling. Reports are generated per plot, which matches how assessors lodge them.
- Name plots the way your assessor references them (plot numbers from the site plan) — the plot name goes into the report filename and the email subject line, so consistency saves questions later.
- Send reports as plots complete rather than batching the whole site at the end. Sending is also what backs your evidence off the single device, so a steady send rhythm doubles as risk management.
What "one device" means alongside this
Unlimited plots applies per capturing device: all of a plot's photos should be taken on the same phone, because photos never sync between devices (by design — see the one-licence article). One busy phone running a whole site is normal usage; one plot split across two phones is the pattern to avoid.
Did this article help?
Thanks. That helps us improve these articles.
Sorry about that. Ask it in your own words, and if our articles don't cover it, it goes to Andrew.