A two-step uploader: the server mints a one-time signed upload URL, then the browser PUTs the bytes directly to storage. The bucket is public so the unauthenticated customer estimate portal can display the files with no proxy. Size is checked client-side with a message suggesting a video link for anything larger.
Also called: upload a testimonial video · attach big plan PDFs · upload failed 413
A walkthrough video shot on a phone goes through
Uploads used to run through a path capped around four and a half megabytes, so any real jobsite video failed with an error that named no cause — builders saw it not work and stopped trying. Files now go straight to storage, up to fifty megabytes, so a full plan set or a customer's video testimonial uploads like anything else.
A file that is too big says how big it is and what to do instead
Anything over the limit is refused before the upload starts with its own size, the limit, and the suggestion to paste a video link instead. An upload that fails silently costs a builder the testimonial; one that explains itself costs thirty seconds.
The same path carries the proof and the plans a buyer reads before signing
Testimonial photos and videos, and the plan and blueprint files attached to a quote, all move the same way and are served straight to the customer's page with nothing standing in front of them. These are the two attachments that do the persuading, and they were the two that were hardest to get onto the page.
Uploads land in your account's own space, started only by your staff
Each file is stored under a path scoped to your account, so nothing another builder uploaded can be guessed or listed by name. Starting an upload requires a signed-in admin, sales or project-manager user — a public page can display these files, but it can never add one.
- 1POST /api/portal-media/sign-upload returns an upload URL and the eventual public URL
- 2The browser PUTs the file directly, so it never transits a serverless function
- 3The 50 MB limit is enforced at the bucket and in the client
- 4The returned public URL is stored on the testimonial or the estimate's plans
Uploads were routed through a path capped at roughly 4.5 MB per request, so any real jobsite video failed with a cryptic error that named no cause — the builder simply saw it not work and stopped trying. Files go straight to storage instead. A walkthrough video shot on a phone uploads like anything else.
- Serverless body limits blocking real media files
- Opaque upload failures with no actionable message
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →