Loading…
Loading…
Jotform to Dropbox, wired so submission files and PDFs land in a folder the team already syncs, named so you can find them.
If your files already live in Dropbox, the Jotform to Dropbox integration keeps it that way. Uploaded attachments and the submission PDF save into a Dropbox folder automatically, so they sync to everyone's machine alongside the rest of your shared files instead of staying stuck in Jotform. For Dropbox-centric teams, it's a set-and-forget connection.
What there is to get right is organization and access. Files can pile into one folder without per-submission subfolders, default names don't tell submissions apart, and a shared folder's membership, not the integration, decides who can open what. The save itself is reliable. The work is making the destination navigable. This page covers how it saves files, how to keep the folder usable, and the handful of gotchas worth knowing before you depend on it.
I spent five years on Jotform's product team. Dropbox was one of the quieter integrations: connect it once and forget it. The questions that came up were about folder structure, naming, and shared-folder access. Here's how to set it up so files stay findable.
In Jotform's Integrations tab you authorize Dropbox access and choose a destination folder. Everything the integration saves goes under that folder unless you configure subfolders. A shared folder makes the files reachable by the whole team.
You decide whether to save uploaded files, the submission PDF, or both. Uploaded files are the attachments from file-upload fields; the PDF is a formatted copy of the submission. Most teams save both.
On submit, Jotform pushes the chosen files to Dropbox. These are durable copies in your Dropbox storage, so they persist even if the original submission is later deleted from Jotform, and they sync to every device on the folder.
Configure a subfolder per submission and name files from form fields so each upload is identifiable. Skip that and everything lands in one folder with default names, which gets unwieldy on busy forms.
An onboarding or intake form collects documents that save into a shared Dropbox folder the whole team syncs. Set a subfolder per client, named from the form, so each client's files stay together and appear on everyone's machine.
Forms collecting design files, photos, or media route them into Dropbox where the creative team already works. Naming files from a form field keeps a busy folder sortable.
Applications or entries save their attachments and a PDF copy to Dropbox as a durable archive that outlives Jotform's retention, synced and backed up wherever Dropbox is.
Saving the submission PDF to Dropbox gives a human-readable backup outside Jotform, pairing well with a Sheets or webhook integration handling the structured field data.
Without per-submission subfolders, a busy form fills a single folder fast, and it syncs that mess to every device. Configure a subfolder per submission and name it from a form field before the form goes live.
Default names don't say which submission a file belongs to. Map a form field into the file name so each upload is identifiable, otherwise reconciling files to submissions later is guesswork.
Who can open the saved files depends on the Dropbox folder's sharing, not on Jotform. If teammates can't see the files, add them to the folder, and conversely, don't save sensitive uploads to a folder that's shared more widely than you intend.
Files count against the Dropbox account's storage quota, so high-volume forms with large uploads can fill it. And standard Dropbox is not a compliant store for PHI or other regulated data without the appropriate agreement and configuration.
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your Dropbox setup, or send me the details first.
This integration is reliable for what it does. Skip it as your only system if you need structured field data (pair it with Sheets, a webhook, or another data store, since Dropbox holds files, not queryable rows). Use a shared folder rather than a personal one so the team can reach the files. And don't route PHI or regulated uploads into standard Dropbox storage without the right agreement and configuration in place.

The onboarding flow every agency wishes they had before their first client was late with assets

Knockout screening, resume routing, candidate tracking. ATS-free for under 10 hires a year.

Camp registration: signup, payment, waivers, waitlists, check-in. One Jotform.
In Jotform's Integrations tab, authorize Dropbox, choose a destination folder, and select whether to save uploaded files, the submission PDF, or both. On each submission the chosen files push to that folder and sync to every device on it. Configure per-submission subfolders and field-based names to keep them organized.
Access depends on the Dropbox folder's sharing membership, not on Jotform. If teammates can't see the files, add them to the shared folder. The integration just places files there; Dropbox controls who can open them.
Yes. Configure the integration to create a subfolder per submission and name it from a form field, which keeps each entry's files together. Without that, everything lands in one flat folder that gets hard to navigate, and syncs that way to every device.
Yes. The integration saves durable copies into your Dropbox storage, so files and the submission PDF survive even if the original submission is removed from Jotform. They then count against that account's storage quota.
Free 20-minute call. I'll tell you which workflow fits your Dropbox setup and what it would take to build, or you can send me the details first.