What's new

We fixed a bug that affected a very specific combination: forms with Save form data as text file turned on, using dynamic subfolders, with an FTP, FTPS or SFTP server as the upload destination. If your form doesn't match all three, you were never affected. Google Drive, Dropbox, Box, OneDrive and SharePoint destinations were fine throughout.

For that small group, the text file was saved under the server's root folder, instead of being saved with the uploaded files. It's now delivered into the same folder as the files, and Save to a different location respects the FTP or SFTP folder you picked. Text files already saved in the wrong place weren't moved, so if this describes your form, it's worth a look in your server's base folder.

The fix is automatically applied to all new submissions and no action is required.

Your Google Sheet can now be laid out the way you actually use it, not the way the form happens to be built. Pick which form fields are written to the sheet and put them in whatever order suits your workflow, so a sheet that feeds a report or an automation holds exactly the columns it needs and nothing else. You'll find this under Choose columns in the Google Sheet card.

Multi-file submissions are more flexible too. If you'd rather count submissions than files, or you want the answers listed once instead of repeated on every row, Rows for multi-file submissions gives you three layouts: one row per file with the answers on each (the current behavior), the answers on the first row only, or the whole submission on a single row with the files together in one cell.

Linking a sheet you already have is safer. EZ File Drop checks the sheet first and, if it has content, tells you exactly which tab will be cleared before you confirm. You can also rename or move the tab the form writes to without breaking syncing. Creating or linking a sheet adds your existing submissions in the same step, and the card shows Rebuilding… while it fills so you know it's working.

If your sheet already has rows, changing the columns or row layout asks you to rebuild it so every row matches, or you can undo and leave the sheet as it is. Forms you don't touch keep working exactly as they do today.

Before this, every sheet got every form field in the order they appeared on the form, a multi-file submission always meant one row per file with the answers repeated, and the tab had to stay named Sheet1.

Send form data to a Google Sheet

When someone uploads five files and their connection drops before the last two files upload, you now get the three files that finished. They're delivered within a few minutes, the submission is marked Incomplete, and a Partial Upload email is sent to tell you what arrived and what's missing so you can follow up with the uploader instead of asking them to start over. Webhooks and Zapier still fire, with the status set to partial so your automations can tell the difference. The email follows the form's failure notification setting.

Statuses are more clear across the board. Submissions now read Uploading (the browser is still sending files), Transferring (files are being delivered to your storage), Completed, Incomplete or Failed, and small chips above the table filter to the Incomplete and Failed ones in a click, so problem submissions don't hide in the list.

Before this, in-progress submissions showed Pending, and a multi-file upload that stopped partway sat for up to 12 hours waiting for the upload to finish before it was marked Failed even though good files had arrived.

View and manage submissions

We improved the way forms get embedded on external websites.

The most notable difference is significantly faster load speeds, with a near 60% improvement.

Auto-sizing is more reliable. URL query parameters now work on embedded forms. And a new transparent background option is available so embedded forms can feel more seamlessly integrated on your page.

Our new embed code uses JavaScript. Previously, embedding used a pure iframe with a separate resize script.

The pure iframe embed code is still available for pages where JavaScript is blocked or not supported.

Embed codes already on your site keep working without any change. To get the benefits of the new embed codes, copy the new code from the Share tab and update the site where your form is embedded.

Embed a form on your website

We listened to your feedback, and you can now embed a form on your own site during the trial and see how it fits before choosing a paid plan.

Embedded forms display the same small line noting they're running on a free trial as the standard share links.

We renamed two settings in the form builder to better describe what they actually are. Form title and Description replace Page header and Page text.

These changes are reflected everywhere: Form Setup, Style mode, the embed display switches and tooltips. Your content and settings are unchanged; only the labels changed.

Incognito and private browser tabs (or any browser extension that blocks third-party cookies) usually won't let Google's folder picker open. When this happens, Google shows a vague error about an invalid API developer key, which is not only misleading, but it doesn't give any information about what the problem is or how to fix it.

We added a behind-the-scenes helper that detects this scenario and provides a clear explanation when this happens. Now, you'll see a message saying Your browser is blocking Google Drive, with what to do about it (use a normal window or allow cookies) and a Try again button. Normal browsers won't see any changes.

If you only have one cloud account connected, selecting an upload destination on a file upload field now opens the folder picker directly. This small change removes three unnecessary clicks from the process. Since most EZ File Drop users only have one cloud account connected, this small change will save most users several seconds every time they create a new form. Small savings add up.