Home Upload pages

Upload pages

Create, publish, brand, and share upload pages.
Stuart
By Stuart •
9 articles

Add questions and set file requirements

Open an upload page and click Add item to add a question, file upload, or explanatory text. Use the field’s settings button to adjust its rules. The Add item menu with uploader details, file upload, question types, and text content. Choose a field Field Use it for Uploader details The sender’s name and optional email identity. File upload One or more files, with count, size, type, and destination settings. Text or text area A short reference or longer notes. Email, number, or date A value with the matching validation. Select or radio group One choice from a consistent option list. Multiple choice More than one selected option. Yes/No or checkbox A decision or acknowledgment. Read-only text Instructions that do not collect an answer. Use Uploader details when you want the sender identified in the submission’s uploader summary. A separate text or email question remains an answer field. The page allows one Uploader details field; enable its email setting if you need that address. Configure a question Give it a label that names the answer you need. Add help text or a placeholder if an example removes ambiguity. In field settings, choose whether it is required or optional. Add choice options before using a select, radio, or multiple-choice question. Use the field’s actions menu to change its order or duplicate it where available. Conditional rules need their source question above the dependent field. Configure file uploads Open the file field’s settings and review the maximum file count, maximum size, and accepted types. The limit applies to that field; explain the requirements in its visible instructions. Changing a filename extension does not convert a file into another format. File field settings used to configure required files and upload constraints. Choose a destination on the file field itself. Use separate file fields for categories that need different instructions or destinations. Free includes one file field per page. Solo and above allow more fields; different destinations per field require Pro or Agency. Keep upload size limits and AI processing limits separate. A file can reach storage while AI processing is skipped or fails. Preview and save Switch to Preview, try the required questions and invalid values, and check the Success content. Preview does not prove delivery to a storage provider. Complete a small upload through the shared link to test delivery. Click Save changes. On an enabled page this affects the live form; on a disabled page, enable it when ready. See page availability.

Last updated on Nov 06, 2026

Create an upload page

Create an upload page for a specific request, such as “Send your onboarding documents.” Your uploader opens its public link, answers your questions, and sends files to the storage destination you choose. The upload page editor with a file request and selected destination. Build the request 1. Open Upload Pages > New upload page. Start from a template or configure your own request. 2. Set the internal name for your team. Set the public title and instructions for the uploader. Explain what to send, any deadline, and what happens next. 3. Add questions with Add item. Use Uploader details for the sender’s identity; enable email if you need it. Add a client reference or document category where useful. 4. Add a File upload field for files. Set its required status, accepted types, maximum size, and file count. 5. On that file field, choose a storage account and destination folder. Connect Google Drive, Dropbox, or OneDrive if needed. Each file field needs a valid destination. 6. Configure folder organization on a supporting plan if answers should name subfolders or files. 7. Review Appearance, Access, and the Success content. Add a page password or expiration if your request needs one and your plan supports it. A page can collect answers without files. You only need storage when you collect files. Check the uploader’s experience Choose Preview. Check the title, instructions, required questions, accepted file types, and success message. Try each branch of any conditional questions. Preview checks the form. To prove delivery, you must submit a small sample through its public link and inspect the result. Enable and share Click Save changes, then use Disabled to enable the page. You can also open Share and confirm Enable and share. Resolve any validation messages first. Copy the Direct link from Share. Send that link to uploaders, or use the embed options for your website. An editor URL opens the workspace and asks for sign-in. The editor toolbar with Save changes, availability, and Share controls. On an enabled page, Save changes updates the live configuration. Disable the page before preparing edits you want to keep closed to new submissions. Read page availability for expiry, plan blocks, and archiving. Verify a sample Open the public link, answer the questions, attach a small file, and submit. Check: - The uploader sees the completion outcome. - The file appears in the chosen cloud folder. - Received shows the expected answers and delivery status. - Any configured Sheet, team email, or external workflow receives the expected output. If enabling fails, review the highlighted field labels, choices, destination, password, and plan requirements. If the upload fails, check storage health before asking for another copy. Next: add questions and file requirements, customize the page, or share links and QR codes.

Last updated on Nov 06, 2026

Customize branding, language, and success messages

Open an upload page’s Appearance settings to choose the public form language and brand style. Use Success to edit what the uploader sees after submission. Appearance settings showing the workspace-brand and custom-page choices. Use the workspace brand Choose Workspace under Brand style to use shared workspace branding. Review the logo, colors, and typeface in Settings > Workspace, or use Edit workspace brand from the page editor. A workspace-brand edit can affect other pages that use that brand. The workspace name used inside the app is separate from the public brand name shown to uploaders. Customize one page Choose Custom to change the page’s appearance without replacing the workspace brand. Pick the logo and supported colors or typography controls shown in the panel. Review a logo before reusing it from saved logos. Workspace branding settings with shared logo and public brand details. The plan controls some branding options. Removing ordinary PigeonFiles attribution is available on supported paid plans; Agency adds white-label behavior, public brand metadata, custom upload domains, and sender domains. Check the upgrade message on the specific control before choosing a plan. For Agency white-label settings, add a public brand name before enabling White-label. Do not claim that removing attribution changes storage permissions, security certifications, or the software that handles an upload. Choose the form language Use Form language to set the uploader-facing interface language. Your personal app language in Profile is separate. Review your own question labels and instructions too; changing interface language does not rewrite the text you authored. Set the success message Choose the Success tab and write the title and message the uploader should see after completing the form. Say what happens next, such as “Our team will review your documents within two working days,” only if your team can meet that promise. The completion message shown in the Success preview. Do not treat that message as proof that a person has reviewed the documents or that an optional automation finished. Check Submissions for processing outcomes. Check the result Preview at a narrow width as well as desktop. Check contrast, logo legibility, long titles, field labels, and success content. Save the changes; an enabled page updates on Save changes. Open its shared link to confirm the public result.

Last updated on Nov 06, 2026

Save, enable, disable, and archive upload pages

Use the page’s Enabled or Disabled control to manage whether people can submit. Click Save changes to save your edits. The editor header showing the page availability control and Share action. Make a new page available Configure the page, then click Disabled to enable it. Enabling saves valid changes and makes the page available. You can also click Share on a disabled page and confirm Enable and share. Resolve the validation messages first if enabling fails. Check field labels and options, the destination of each file field, password requirements, and settings your current plan supports. A page can collect answers without a file field; a file-collection page needs its file field and valid destination. Save changes to an enabled page Click Save changes after editing. On an enabled page, a successful save updates the live configuration for new submissions. You do not need another publishing step. Disable the page first if you want to prepare changes while new submissions are closed. Save the changes, preview them, then enable it when ready. Unsaved local edits do not survive leaving the editor unless you save them. An active save keeps the existing Free-plan availability window. Repeated saves do not extend its closing time. Stop new submissions Click Enabled to disable the page. On narrower screens, open More upload page actions if the control is not visible in the header. Existing submission records remain available. Check any in-progress submission before asking its uploader to retry. Re-enable a paused page when it is ready. If you edited it while paused, review the new configuration before enabling it. Resolve expiry or a plan block Free pages have a three-day availability window. If the app says that window ended, enable the page again to open another window. Paid plans have no plan-imposed page lifetime; an explicit closing date can still apply. Under Access, review Expiration. A page with an original closing date carried from the older product keeps that boundary on Free; republishing does not extend the original lifetime. Follow the in-app expiry notice rather than promising another three days in that case. After a downgrade, settings outside the new plan can block the page. Remove or change the flagged settings, or restore a plan that supports them. Saving a valid replacement and enabling it is different from deleting the page. Archive, restore, or duplicate Use More upload page actions > Archive when the request should leave the active collection. Archiving closes it and retains its settings and history. Use View archived, open the page, and choose Unarchive upload page to restore it; review availability before sharing it again. Use Duplicate to start another request from a page’s saved structure. Save or discard local edits first. The copy has its own identity and link; check its destinations, fields, access, and automation settings before enabling it.

Last updated on Nov 06, 2026

Find, reuse, and organize upload pages

Open Upload Pages to find your workspace’s requests. Check the workspace selector first if a page is missing; pages belong to their workspace. A client file request template preview with its questions. Start from a template Choose New upload page and select a template that fits the request. Review its questions, file fields, and instructions. Set your own destinations and check access and automation settings before enabling it. Template examples do not prove that your storage or automation is configured. Use Create an upload page for the full setup flow. Find and reuse a page Search or use the available filters in Upload Pages. Open the editor to inspect the public title and internal name. Use the internal name for your team’s reference; the public title addresses the uploader. To reuse a saved structure, open More upload page actions > Duplicate. Save or discard local changes first. Check the new page’s link and settings before sharing; a copy has its own identity. Existing submission history remains associated with the original page. Organize with tags Use Add tags beside the internal name in the editor to label a request for your team. Use the list’s available tag filters to find related requests. Tags organize pages; they do not grant access to another workspace. Find archived pages Choose View archived. Open a page and use Unarchive upload page if you need it again. Check its destination, plan compatibility, expiry, and availability after restoring it. Archiving closes collection and removes a page from the usual active view. It is different from disabling a page for a short edit. See Save, enable, disable, and archive pages. If a teammate cannot find it Confirm the workspace, invitation status, and role. Share a public link with uploaders and an editor link with workspace members. A public link does not grant access to workspace settings.

Last updated on Nov 06, 2026

Protect an upload page and set its closing date

Open Access in the page editor to review how people reach the request. A public link lets its holder open the page; a shared password adds a page-level check on a supporting plan. Access settings for access mode, expiration, and search indexing. Add a password Choose the password access mode and set a password that meets the displayed requirements. The editor requires at least eight characters. Save the change, then test the public link in a private browser window. Give the password to the intended uploaders through a suitable channel. A page password belongs to the request. Uploaders do not use their Google, Microsoft, or PigeonFiles account password. It does not identify an individual sender or change cloud folder permissions. The password prompt an uploader sees. If an uploader reports a rejected password, check the current saved setting and resend it without extra spaces. Change the page password if the request’s audience changes. Set a closing date Review Expiration and choose the closing date offered for your page. Save and check the resulting availability notice. A paid plan removes the Free plan’s three-day lifetime; an explicit closing date can still close the request. On Free, saves to an enabled page do not extend its current availability window. A page carried from the older application may retain its original closing boundary. Follow page availability for renewal and expiry behavior. Control search indexing Review the Search indexing setting. Blocking search indexing asks compliant search engines not to index the public page; it does not authenticate visitors or stop someone opening a shared link. Use access controls appropriate to the information you collect. Close collection now Use the Enabled control to disable the page. Archive it when you want it out of the active collection. Check existing submissions before asking anyone to resend files. For sensitive workflows, review file access and storage responsibilities.

Last updated on Nov 06, 2026

Share an upload link or QR code

Use the upload page’s Share dialog to send uploaders its public URL. An editor URL is for your workspace team and can ask recipients to sign in. The Share dialog showing the public link and QR-code action. The screenshot uses a demonstration address. Copy the link from your own page. Copy the public link 1. Open the intended page in the correct workspace. 2. Click Share. 3. If the page is disabled, review and confirm Enable and share when ready. 4. Click Copy beside Direct link, or copy the link text. 5. Test that link in a private browser window before sending it. Password-protected pages still ask for the page password. Send the password through an appropriate separate channel; a QR code does not bypass it. An expired, disabled, archived, or plan-blocked page can also stop accepting uploads. Use a custom-domain link When an eligible workspace has a verified upload domain, Share offers the Custom domain link and an App-hosted fallback link. The fallback is useful while you diagnose the custom domain. See custom-domain setup. Download a QR code On a plan with QR sharing, open the QR code options beside the link. Choose Download SVG, Download PNG, or Copy PNG. If your browser does not support copying PNG images to the clipboard, download the PNG instead. Check the destination before printing or distributing the code. Scan a sample using another device and complete a small test submission. The QR code opens the same page and remains subject to its access and expiry settings. Put the form on a website Use Copy iframe code in Share, or the matching website-builder integration. Review Embed an upload page for iframe height, JavaScript allowed origins, and testing inside the surrounding website. The recipient sees a sign-in screen Compare the URL you sent with the public link in Share. Replace an internal /upload-pages/.../edit link with the copied public URL. Uploaders do not need workspace accounts.

Last updated on Nov 06, 2026

Show and require fields based on earlier answers

Use conditional rules when an earlier answer determines which question an uploader needs next. Pro and Agency include conditional logic. For example, ask whether extra project details are needed, then show and require a details question when the answer matches your rule. An upload form showing the follow-up field after its source answer matches a condition. Add a visibility rule 1. Add the question that supplies the answer. 2. Place the dependent question below it. 3. Open the dependent field’s settings. 4. Change its visibility from Always show to Show when. 5. Choose the earlier field, an operator, and the value to match. 6. Choose whether all conditions or any condition must match if you add several. The available operators depend on the source field: text matching, selected options, numbers, dates, and whether a file is present need different comparisons. Choose a valid option from the control rather than typing an obsolete choice label. Require an answer under a condition Use the field’s Required when setting to define when an answer is mandatory. Visibility and requiredness are separate rules. Review both so you do not display an optional question when the workflow needs an answer. Move the source question above the target if the editor says Add a field above this one to continue. Review dependent rules after changing or removing a source question or choice. Test each branch In Preview, enter an answer that should reveal the field, then one that should hide it. Submit with a missing conditional answer to check the required validation. Repeat for each combination you expect uploaders to use. Save the page only after the branches behave as intended. Save changes updates an enabled page. Disable it first if you need to prepare the change away from live intake. A rule does not behave as expected Check the field identity, order, chosen operator, match value, and whether the rule uses all or any conditions. A field with the same label is not the same field after you delete and recreate it. Conditional visibility helps present a form. Do not use it as authorization for sensitive information. Keep secrets and privileged identifiers out of the form configuration. For file destinations based on answers, use the routing guide as well as the field-visibility rule. Compare both branches This example asks for project details only after the uploader enters “yes.” Check both the hidden and visible states, including the required-field behavior. The follow-up question hidden before the matching answer.

Last updated on Nov 06, 2026