Forms
Export form responses to CSV
The export gives you a CSV with a submitted-at column and one column per input field, covering every response rather than the page you are looking at. Knowing how the composite fields are written is what saves you an afternoon later.

One column per field
Columns are named after your field labels, in form order, with Submitted At at the front. The export pages through the whole response set rather than exporting the current page, so a form with four thousand responses exports four thousand rows.
How composite fields are written
They are joined into their single column rather than expanded. A matrix becomes each statement and its answer separated by pipes. An address becomes its parts joined by commas. A full name becomes one name. A table becomes a JSON array of the filled rows. Fill in the blank becomes the blank values separated by pipes.
Uploads and signatures
A signature writes as the literal text marking a signature image, and a recording writes as a note that a recording was uploaded. Files are not in the CSV, because a CSV cannot hold them. Download them from the responses table or take the response PDF, which merges attachments in.
Design for the export
If a question will be counted or averaged, ask it as its own choice field rather than as a row in a matrix, because a single choice field is already its own column. A matrix is friendlier to fill in and harder to analyse, and knowing that before you build the form is worth more than any amount of spreadsheet work afterwards.
How it works, in three steps
Step 1
Name fields as you want the columns named
The field label becomes the column heading, so a label that reads well on screen and badly in a spreadsheet is worth changing.
Step 2
Export the whole set
The export pages through every response, not the page on screen.
Step 3
Split composites if you need to analyse them
Matrix and address columns are joined in a fixed order, so splitting them in the spreadsheet is reliable.
The full walkthrough with screenshots is in the guide View, export and manage your responses.
Limits worth knowing
- One column per field. Composite fields are joined, not expanded.
- Uploaded files are not in the CSV. Take them from the responses table or the response PDF.
- Signatures and recordings are noted as text, not embedded.
See it on a finished piece
Questions people ask
Does the export include every response or just the current page?
Every response. It pages through the whole set in batches and writes them all into one file.
How is a matrix exported?
As one column, with each statement and its answer separated by pipes. If you need to average one statement, ask it as its own question instead.
Where are the uploaded files in the CSV?
They are not. A CSV cannot carry files. Download them from the responses table, or use the response PDF, which merges attachments into the document.
Make your own form
The button opens the generator with this use case already described. Change the wording to match yours, generate, then edit anything you like.
Create a form with OneCraftRelated pages
Read and manage form responses
Every submission is a row, with a column per input field and the submission time at the front. Composite answers like a matrix, an address or a table are readable in the cell, so you can scan a page of responses without opening any of them.
Download a form as a PDF
Not everyone will use the link. A blank template PDF gives you the same form as a printable page, laid out properly rather than screenshotted, with a header, a footer and page numbers.
Make a fillable PDF from a form
A fillable PDF is a document with real form fields in it. People open it in any reader, type into the boxes, save it and send it back. It is what you need when the recipient will not use a link but will use a computer.
More finished work of this kind is on the form examples hub.


