Does Govform support file uploads?
Yes, absolutely. Govform supports large uploads, multiple files and streaming bulk-data processing, with your choice of storage, antivirus scanning, document reconstruction and image privacy controls.
Whether you collect a supporting document, a substantial evidence pack or a large reporting dataset, you can control what people upload, how it is checked and where it goes. Use our managed file store or connect your own.
Handle large files and complete evidence packs
- Large uploads. Configure standard uploads up to 20 GB per file, subject to the chosen storage and protection settings. Set a lower limit wherever your service needs one.
- Multiple files. Collect up to 100 files in a multiple-file component, with a separate size limit for each file.
- Clear evidence requirements. Restrict extensions or MIME types, make uploads mandatory where needed, and use conditional questions or pages to request only relevant evidence.
- Easy checking and review. Show filenames, file view links or download links on Check Answers pages, so users and authorised reviewers can inspect the evidence.
Process substantial CSV and Excel submissions
Bulk Data goes beyond storing a spreadsheet. Govform uses streaming, row-by-row processing to validate CSV files or a selected XLSX worksheet in the background, making it suitable for substantial structured returns.
- Validate at scale. Support datasets with up to 5 million data cells across up to 200 configured columns—for example, 500,000 rows with 10 columns.
- Define what good data looks like. Check required values, text lengths, integer and decimal ranges, dates, true/false values, permitted choices and uniqueness.
- Help respondents resolve problems. Present validation results and, when enabled, let people correct selected batches of up to 1,000 rows before confirming the dataset.
- Keep source and validated data distinct. Retain the original upload alongside the confirmed CSV, including respondent corrections, so downstream systems receive the version you intend.
- Move large datasets onward. Stream the confirmed CSV or original source to a configured file store, or retrieve it through the streaming download API.
Use our file store or yours
| File store | What it gives you |
|---|---|
| Govform managed storage | A platform-managed destination for your service evidence, with integrated retrieval, retention handling and in-place antivirus scanning when configured. |
| Your SharePoint site | Collect evidence into your selected site and folders, alongside the documents and permissions your team already uses. |
| Your Amazon S3 bucket | Store files in your own configured bucket, with your organisation's storage policies. |
| Your Google Cloud Storage bucket | Keep uploaded evidence within your configured Google Cloud storage. |
| Your Azure Blob Storage container | Send evidence into your configured Azure container and existing storage arrangements. |
Normal Govform view and download links work with the configured stores, so using your own storage still gives people a joined-up service experience. External stores retain their own access and retention policies.
Choose how files are scanned and protected
For customer-owned stores, Govform antivirus scanning is optional. You can add our checks to your storage arrangement or use the destination's own controls:
- Scan before transfer. Govform checks the file first and transfers it to your store only after a clean result.
- Scan in parallel. Run the Govform scan alongside the destination upload. A detected threat rejects the upload and triggers removal of the destination copy.
- Use your own scanning arrangements. Transfer without a Govform AV scan when your organisation chooses to rely on its own storage and security controls.
Govform managed storage uses in-place scanning when the platform's scanning service is configured. CDR follows a scan-first process and requires the original to pass scanning before reconstruction and transfer.
| Capability | What it does |
|---|---|
| Content Disarm and Reconstruction (CDR) | Reconstruct supported documents and images to reduce risk when reviewers open evidence. CDR is available on single-file components, with a separate processing size limit. |
| Face blurring | Detect and blur faces in JPEG or PNG images through CDR image processing, reducing unnecessary exposure of people in photographs. |
| Metadata removal | Strip GPS, camera, timestamp and other metadata from JPEG or PNG images before storage or onward transfer. |
| Image resizing | Automatically reduce large JPEG or PNG images to Full HD dimensions to keep evidence manageable. |
File sizes and processing limits at a glance
| Upload or processing route | Limit |
|---|---|
| Standard uploads | Configurable up to 20 GB per file. Storage, scanning and service policies can impose lower limits. |
| Multiple-file components | Up to 100 files per component; the configured size limit applies to each file. CDR uses a single-file component. |
| Bulk Data CSV/XLSX | The source file follows its upload component's size limit. Validation supports up to 5 million data cells and 200 configured columns. |
| CDR-protected uploads | 50 MB by default, or the component's limit if lower. The platform's configured CDR processing cap determines the maximum. |
| Govform AV for external stores | The current scanning transfer supports files up to 5 GB; a lower component or destination limit still applies. |
| Files embedded in API requests | 25 MiB of combined raw files per API action, with Base64 encoding adding approximately one third. Use file-store transfers or streaming downloads for larger evidence. |
For evidence-heavy services, you can choose a large-file route and the right level of protection separately. We can help match the upload limit, scanning mode and destination to your operational requirements.
Explore file components, upload actions and Bulk Data files and integrations, or discuss your evidence requirements with us.
