Start with the file's type and size, the field settings and the exact error. Uploading a file stages it; only a successful accepted submission or entry edit attaches it to the entry. Do not treat a progress bar alone as a saved submission.
Check the limits that apply
| Setting | What it does |
|---|---|
| File type | The field must allow the extension and the server must accept the actual file. Renaming a disallowed file is not a valid conversion. |
| Per-file size | The effective limit is the lower of Maximum file size and the host's upload limit. Raising only the field value cannot raise a PHP or proxy limit. |
| File count | Single mode allows one. Multiple mode uses Maximum files, from 1 to 50. Remove an existing selection before adding beyond the limit. |
| Staging and storage quota | Separate source, site staging and total-storage budgets apply across forms. Defaults and configurable host limits are described in the File Upload guide. A source may be shared by visitors behind one address. |
Pending upload, Retry or disabled picker
Wait for active uploads to finish before Next or Submit. A failed row needs Retry or removal. At the file-count limit, the picker remains visible but disabled and extra drops are ignored. Removing a file restores capacity.
With JavaScript, inspect the failed upload request and its safe error. Without it, the native multipart form checks limits on submit. If the entire request is missing or too large before WordPress receives it, ask the host to check request-body and PHP limits. A reverse proxy can impose another limit.
A staged reference belongs to its form, field and browser attempt. A different tab/visitor, stale form version or expired attempt cannot claim arbitrary staged files. Reload a fresh form when requested; do not substitute attachment IDs manually.
Storage or quota failure
Have the host confirm available disk space, writable configured storage and correct filesystem permissions. An invalid LFORMS_UPLOAD_PRIVATE_DIR deliberately fails uploads. The path must be durable and outside document roots, not an operating-system temporary directory.
Temporary files normally expire after 24 hours and wait for cron or later opportunistic cleanup. Expired files and files awaiting a failed deletion retry can still consume capacity until removed. Do not manually delete attachment rows or storage directories to clear a quota: entry references and file ownership must remain consistent.
A saved file link fails
Use the link from the current saved entry. It needs a committed retained file reference, a valid token, the active plugin and the physical file at its recorded path. Temporary uploads do not have public preview/download URLs. Permanent removal, a lost file during migration or a missing plugin can explain an old link failing.
Check HTTPS and bypass page/CDN caches for logical_forms_file requests. Backups and site transfers must include every current or previously used file directory; changing the private storage path affects new files only. Offloaded or alternate media storage requires its own integration.
Committed download links are accessible to anyone who has them. They are not login- or role-protected. Default storage may also be directly served by the host if a raw URL is known. Review access requirements before collecting sensitive files.
Replacement or removal did not persist
On an owner or staff edit, Save changes commits file changes. A failed replacement retains the old file; unused new files expire through cleanup. Trash retains entry files. Permanent entry deletion and confirmed upload removal reconcile owned files, separately from exported copies or email attachments.
Useful diagnostic details
Provide the form and field IDs, timestamp/timezone, file extension/size, configured limits, error code and request status. Include Core/add-on versions and whether the failure is staging, final submission, editing or downloading. Do not share confidential file contents or working download tokens in a public report. See File Upload and upload validation messages.
