Upload Directory Setup
Using the signer file upload field
The file upload field lets signers attach a file while they sign. Common uses include a photo ID, a supporting PDF, or an image.
What signers see
When you add an upload field to your document, you can set a label, mark it required, and limit which file types and sizes are allowed. When someone signs, they choose a file from their device. After signing, they (and any recipients you allow) can open the attachment using the download link on the completed document.
Allowed file types
Typical allowed types are images (JPG, PNG, GIF) and PDF. The exact options depend on your field settings and plugin version. If an upload is rejected, the error message usually points to a file type or size issue. Check the field's advanced settings and your server's upload limits in your hosting control panel or php.ini .
Where files are stored
Uploaded signer files are saved to:
wp-content/uploads/esign/
The plugin manages filenames on disk — you don't need to track the signer's original filename. To open an uploaded file, use the download link on the signed document. You don't need to locate the file on the server directly.
After the document is signed
Attachments are tied to the signature record. Recipients access them using the Download control on the signed document or PDF. Download links are built to stay usable over time, including when someone opens an older completed document.
Optional: server-specific notes
Most sites don't need to change anything here. The notes below are for teams who want their upload folder to match how their server is configured.
Apache
On Apache, the plugin can place an .htaccess file in the esign folder to restrict direct access. If your host disables .htaccess in uploads, they can apply the same restriction in the main site config. Your host support can advise.
Nginx
Nginx does not read .htaccess files. If your team manages Nginx directly, they can add a location rule for /wp-content/uploads/esign/ to match your site's hardening policy. This is optional and not required for the upload field to work.
For copy-and-paste configuration examples and more information, see our upload directory protection documentation here.
Custom folder (developers)
If you store sensitive uploads outside the public web root, a developer can redirect signer file storage using the WordPress filter esig_file_upload_path . Use an absolute path, set correct file permissions, and make sure the folder is included in backups and migrations.
<?php
// Example only — use a real path and test on staging first.
add_filter( 'esig_file_upload_path', function ( $path ) {
return '/path/outside/public_html/my-esig-uploads';
} );
Summary
| Topic | Takeaway |
|---|---|
| Everyday use | Add the field, configure label/required/limits, signers upload and download via the document. |
| Storage | Files are saved to wp-content/uploads/esign/ by default. |
| Apache / Nginx / custom path | Optional — only relevant for teams standardizing server configuration across sites. |