The form user uploads a file, but it does not reach onOffice — or the form stops working during the upload. Here are the most common causes.
propform accepts files up to 128 MB per individual file — this is the server-side nginx limit. Larger individual files are rejected by the server before they even reach propform.
If your file is larger:
The propform API user requires write permissions for files in the relevant module (address or property).
Solution: Check API permissions — see onOffice API user permissions.
If you have selected a document attribute in the field settings (only for property file uploads), check in onOffice whether this document attribute still exists and is active.
Common error: You have renamed or deleted a document attribute in onOffice. propform stores the ID and can no longer map the renamed document attribute.
Solution: Edit the file upload field in propform and reselect the document attribute.
If you have assigned a document attribute and still want the visitor to upload multiple files: this is not possible at API level (1 attribute = 1 file).
Symptoms: Only the last uploaded file ends up in onOffice; the others are silently discarded.
Solutions:
If the file is to be published on a website upon activation (e.g. an image for an online property listing page), the API user requires the “Marketing (Website)” permission.
If you are combining multiple files into a ZIP or PDF file:
PDF bundling only works with images (JPG, PNG, HEIC) and PDF files. Other file types (Word, Excel, ZIP, video) cannot be combined into a single PDF.
Solution: Either select ZIP bundling (works with all file types) or have the files uploaded individually.
If the “Merge multiple files into a single PDF” option is enabled and one of the uploaded PDF files is password-protected (e.g. Vonovia energy performance certificates, some bank PDFs), the PDF merge will fail. propform then automatically falls back to ZIP bundling — the recipient receives a ZIP file instead of the expected PDF.
> 💡 The fallback applies only when the merge option is active. For single-file uploads or multi-uploads without the merge option, the file processes normally.
Workarounds:
Works with all file types. If it still fails, check:
/, \, :, * are not permitted in filenames)iPhone images in HEIC format are automatically converted to JPEG by propform before uploading to onOffice. You don’t need to do anything. If this still fails, please drop us a quick line — very rarely, there are faulty HEIC files.
On the iPhone, the file upload field has a catch:
Workaround for uploading multiple photos from a mobile phone:
> ⚠️ Important distinction — generic upload field vs. file field from the onOffice form: > - The generic “Upload file” field (top field in the module selection) allows multi-upload > - File fields created in the onOffice address/property form (e.g. “Energy Performance Certificate” field) allow only ONE file — this is an onOffice API limitation and cannot be changed
Very long file names or file names containing unusual special characters can cause problems in onOffice. propform automatically cleans up typical cases, but very exotic characters (e.g. Arabic script in the file name) can lead to issues.
Solution: Define a file name with macros in the field settings — e.g. Anfrage_Name_Vorname — then the file name will be automatically generated correctly.
If you outside of propform (manually, not via a form), these files do not appear in the API call GetEstateFiles / GetAddressFiles — so propform cannot process them further or offer them via the download form.
Background: onOffice API limitation — files in the form’s file fields are not directly accessible via the API.
Workaround: Always upload files via the propform form — propform first places them in the ‘Files’ tab and then references them in the file field. This makes them accessible via the API.
Please email us at hello@propform.io with the following information: