How to Share Multiple Files With One Link
Choose between a ZIP, shared folder, and document workspace, then test access to the whole file collection.

On this page (8 sections)▼
To share several files with one link, choose between a ZIP, a shared folder, and an organized document workspace. A ZIP provides a downloadable package; a folder supports ongoing file access; a document workspace can guide the reader through several resources.
Choose the method around the recipient's task, then check every file and permission in the collection.
1. Choose the collection method

One link can point to very different experiences.
| Method | Useful for | Main tradeoff |
|---|---|---|
| ZIP archive | A fixed final handoff | Requires downloading and extraction |
| Shared folder | Ongoing collaboration or storage access | Navigation and permissions need care |
| Document microsite or workspace | A curated reading path | Setup and publishing entitlement |
| Formal deal room | A controlled staged review | More administration than a simple pack |
Avoid selecting a complex room just because several files exist. A small fixed delivery may work well as a labeled archive; an external review may benefit from browser navigation.
2. Remove files the recipient does not need
Inventory the pack before uploading. A working folder often contains drafts, duplicated exports, and internal supporting material.
For each item record:
- File title and format.
- Purpose for the recipient.
- Approved version.
- Whether downloading is necessary.
- Whether it needs a different access policy.
If one document requires narrower access, consider a separate collection or a supported folder-level restriction. Do not assume the entry-page policy covers every direct file link automatically.
3. Organize a clear reading order

Put the overview first, followed by the files needed for the decision. Name files by purpose rather than internal shorthand.
A client proposal pack might contain:
- Start here: proposal overview.
- Scope and deliverables.
- Pricing summary.
- Product demonstration.
- Next steps and contact.
This is an illustrative architecture, not a live client room. For a ZIP, include a short readme. For a workspace, use clear titles and folder names so the reader does not have to guess which item matters.
4. Create the chosen collection and set access

SendNow describes a MicroSite as a multi-file hub shared through one link. Its creation help outlines adding content and configuring the resulting collection. SendNow: Create a MicroSite
If using it, check the current publishing and plan requirements before building the pack. A document-link subscription should not be assumed to include every microsite entitlement.
For a shared folder, use your approved storage platform and set permissions for the intended audience. For a ZIP, review the archive contents before hosting it. Each approach still needs recipient testing.
5. Test the whole collection as a recipient

Open the collection outside your owner session and follow the intended reading order. Test every file, not just the opening page.
| Check | Expected result |
|---|---|
| Entry link | Intended recipient can enter |
| Navigation | File purposes are clear |
| Each document | Correct revision opens |
| Media | Required audio or video plays |
| Downloads | Match the intended policy |
| Restricted material | Is not exposed through another path |
Record actual results if you perform the test. A attractive landing page is not evidence that the underlying files are usable.
6. Share one clear starting point
Explain where to begin and what response you need:
Here is the proposal pack. Please start with the overview, then review pricing and the demo. Let me know which implementation questions you would like us to cover.
Keep a manifest of the shared versions. When a file changes, check whether existing links update or a new file must be issued. Notify readers about material changes, particularly if they may already have downloaded a copy.
For an approved final handoff, retain an appropriate delivery record rather than relying solely on activity metrics.
Frequently asked questions
Should I use a ZIP or a browser workspace?
Use a ZIP when the task is receiving a fixed downloadable package. Use a workspace when reading order, browser access, or updates add meaningful value.
Do collection permissions cover every file?
Not automatically in every service. Check inheritance, direct links, and any file or folder overrides.
Can a collection mix PDFs, slides and video?
Only if the chosen platform supports the required formats and playback. Test each actual item before sharing.
Before you share
One link is useful when it leads to a clear, usable pack. Choose the method, remove unnecessary files, and verify the complete recipient journey.
Related articles
Sources and editorial disclosure
Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.
VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.
Related Guides & Research
Recommended next reading for deal teams and transaction leaders.
Share Files Without a Recipient Account
Choose an account-free viewing workflow while retaining the access checks appropriate for the material.
How to Share Large PDF Files
Choose a delivery method for a large PDF and verify size limits, readability, and recipient access.
How to Share a PDF as a Link
Turn a PDF into a browser link and test the recipient experience before sending it.