How to send a client one page with all their deliverables

There is a particular kind of dread that comes with finishing a project. Not the work itself, but the handoff. You have a brand guidelines PDF, a set of social templates, a handful of video exports, an invoice, and maybe some raw working files the client asked to keep. These sit across your desktop, a shared drive, and your project management tool. Now you need to get them to the client in a way that feels professional, is easy to access, and does not require them to sign up for anything.

Most agencies and freelancers default to one of two approaches. The first is a long email with multiple attachments or a string of download links. The second is a shared folder on Google Drive or Dropbox, which inevitably turns into a maze of nested subfolders, outdated versions, and permission requests. Neither feels like a finished product. Neither tells you whether the client opened anything or downloaded what they needed.

Fabric takes a different approach. You organise deliverables in a folder, hit publish, and get a single link. That link opens a clean, branded page where your client can view every file inline, without downloading anything first and without creating an account. You can lock it with a password, track exactly when the client opens it, and update the contents at any time by editing the source files in your workspace.

This guide walks through the full process, from folder setup to sharing the final link, with notes on security, analytics, and keeping things tidy across multiple clients.

Organise first, publish second

The published page mirrors what is in your Fabric folder, so the time you spend organising pays off directly. Create a folder for the client or project. Inside it, drop every deliverable the client needs: design files, documents, presentations, videos, spreadsheets, whatever the project produced.

Fabric's cloud drive stores everything with zero local storage on your end. Files stream on demand, so you are not juggling disk space or syncing issues. This matters when you are handling large video exports or high-resolution design files that would clog a traditional cloud folder.

If you want to give the client a sense of structure, use subfolders. Group things logically: "Brand Assets," "Social Templates," "Contracts." The published page will reflect this hierarchy, so your client sees a tidy, navigable layout rather than a flat dump of files.

For agencies managing multiple projects simultaneously, Fabric's kanban view can help you track which deliverables are complete and which are still in progress, so you only publish when everything is ready.

Publishing a folder as a single page

Once your folder is organised, publishing it is a single action. Select the folder and use Fabric's publish feature to generate a shareable link. The result is a web page that displays every file in the folder with a built-in viewer. Your client can scroll through PDFs, preview images, watch videos, and read documents without downloading anything or installing software.

This is not a file listing with download buttons. It is a proper viewing experience. Fabric renders files inline, which means your deliverables are presented the way you intended them to be seen, not as a stack of icons waiting to be clicked.

The page works with any file type you would typically hand off to a client. Design exports, slide decks, spreadsheets, contracts, video cuts, audio files, and raw assets all render in the viewer. Your client does not need a Fabric account, a specific app, or any particular software. They open the link and everything is there.

Controlling access with password protection

Not every deliverable page should be open to anyone with the link. Client work is often confidential, especially in the early stages of a brand project or before a public launch. Fabric lets you add password protection to any published page, so only people with the password can view the contents.

Set a password when you publish, then share it with your client separately. This is a simple layer of access control that does not require your client to create an account or remember login credentials for yet another platform. They visit the link, enter the password, and see their deliverables.

For agencies working with enterprise clients who have strict data handling requirements, it helps to know that Fabric uses AES-256 encryption and holds CASA Tier 2 certification. You can point to these standards when a client's legal team asks about security.

Knowing when your client opens the page

One of the persistent frustrations of client work is the silence after handoff. You send the deliverables and then wait, unsure whether the client has looked at anything or is simply busy. Follow-up emails asking "Did you get the files?" feel awkward and do not inspire confidence.

Fabric's link analytics remove the guesswork. Once you share a published page, you can see when the client first opened it, how much time they spent viewing, and whether they returned for additional visits. This data is useful in a few practical ways.

If you see the client opened the page and spent fifteen minutes viewing files, you know they have seen the work and can follow up with a targeted question about feedback rather than a generic check-in. If a week passes and the analytics show no views, you know the link might have been buried in their inbox and a gentle reminder is warranted. If the client keeps returning to a specific section, that might signal they are sharing it internally or have questions about those particular deliverables.

This kind of visibility turns the handoff from a black box into something you can act on.

Updating deliverables without sending a new link

Projects rarely end cleanly on the first pass. Clients request revisions, additional formats, or last-minute additions. With email-based handoffs, this means sending another round of attachments and hoping the client uses the latest versions. With shared drives, it means uploading new files and hoping the client notices.

With Fabric, you edit the source files in your workspace. The published page updates automatically because it is tied to the folder contents. Your client visits the same link they already have and sees the current versions. No new link to share, no confusion about which email has the right files, no version conflicts.

This is particularly valuable for ongoing client relationships. An agency managing a retainer client's brand assets can maintain a single published page that always reflects the latest approved versions. The client bookmarks the link once and returns to it whenever they need something.

Adding context with annotations and comments

Deliverables sometimes need explanation. A set of logo variations might need notes about which version is for print and which is for screen. A video export might need a callout about the codec used. A contract might need a highlight pointing to the section that changed.

Fabric's annotation and commenting tools let you add this context directly to the files. Your client sees the notes alongside the deliverables, which reduces the back-and-forth that comes from sending files without explanation. Clients can also leave their own comments, turning the published page into a lightweight feedback loop rather than a one-way delivery.

This keeps conversations attached to the work itself, rather than scattered across email threads where context gets lost. For freelancers who handle multiple clients, having feedback tied to the deliverable file saves time that would otherwise be spent hunting through inboxes.

Scaling the process across clients

When you are handling one client, any system works. The challenge is when you have ten or twenty active projects, each with its own set of deliverables at different stages of completion. The folder-and-publish workflow in Fabric scales naturally because each client gets their own folder, their own published page, and their own analytics.

For agencies that want to go further, Fabric's organisation features and collaboration tools let team members work within the same workspace. A designer can drop final exports into the client folder, a project manager can review and organise them, and an account manager can publish and share the link, all without leaving Fabric.

Fabric also functions as an AI knowledge base for client relationships, with self-writing documents that can automatically track project details, preferences, and history. The self-writing docs feature builds and updates these records as you work, so you always have context on what was delivered, when, and what the client's preferences are. This memory persists across projects, which means the second engagement with a client starts with all the context from the first.

A practical example

Suppose you run a small design studio and you have just wrapped a brand identity project. The deliverables include a brand guidelines PDF, logo files in SVG and PNG, a set of social media templates in Figma export format, a colour palette reference sheet, and a final invoice.

Create a folder in Fabric called "Acme Co - Brand Identity." Drop all the files in, perhaps with subfolders for "Logos," "Templates," and "Documents." Publish the folder. Set a password. Share the link and password with your client in a brief email: "Here is everything from the project. Open the link, enter the password, and you can view and download anything you need."

Your client opens the link on their phone during a commute, scrolls through the brand guidelines, and checks the logo files. You see the analytics update. Two days later, they return and spend time on the social templates, probably sharing them with their marketing team. You follow up with a specific note about template usage. The entire exchange is smooth, professional, and requires no technical overhead from either side.

Frequently asked questions

Does my client need a Fabric account to view the published page?

No. Published pages are accessible to anyone with the link, or anyone with the link and password if you have set password protection. Your client does not need to sign up, log in, or install anything. They open the link in any browser and view everything inline.

Can I publish a page with mixed file types?

Yes. Fabric's publish feature works with any file type. You can include PDFs, images, videos, audio files, spreadsheets, slide decks, and design exports in the same folder, and they will all render in the built-in viewer on the published page.

What happens when I update a file in the folder after publishing?

The published page reflects the current state of the folder. When you edit, replace, or add files in your Fabric workspace, those changes appear on the published page. Your client does not need a new link.

Can I see whether a specific file was viewed, or just the page overall?

Link analytics show when the published page was opened, how long the viewer spent on it, and whether they returned. This gives you a clear picture of engagement without tracking individual file opens.

Is the published page secure enough for confidential client work?

Fabric uses AES-256 encryption and holds CASA Tier 2 certification. Combined with password protection on the published page, this provides a level of security suitable for most professional client work. For clients with specific compliance requirements, you can share these certifications as part of your data handling documentation.

Can multiple team members contribute to the same client folder before publishing?

Yes. Fabric's collaboration features allow multiple team members to add, edit, and organise files within the same workspace. This means designers, copywriters, and project managers can all contribute to a client folder, and the person responsible for client communication can publish and share the final page.

How is this different from sharing a Google Drive or Dropbox folder?

Three main differences. First, the published page has a built-in viewer, so clients see rendered files rather than a list of filenames. Second, password protection and link analytics are native features, not add-ons. Third, Fabric's cloud drive uses zero local storage and streams files on demand, so large deliverables do not create sync or storage problems. You can read more about this in our guide on sharing files with clients without Google Drive.

Can I use the published page as an ongoing client portal?

You can, and many agencies do. Because the page updates when the folder contents change, it works well as a living resource that the client bookmarks and returns to over time. For a more detailed setup, see our guide on how to set up a client portal.

Can I restrict access so a client only sees their own files?

Yes. Each published page is tied to a specific folder, so clients only see what you put in that folder. For more granular approaches to file-level access control, see our guide on giving a client access to only their files.

What file size limits apply to the published page?

Fabric's cloud drive handles large files without issue because everything streams on demand. There are no practical file size limits that would affect typical client deliverables like video exports, high-resolution images, or large PDF documents.

Related pages

• How to set up a client portal

• How to give a client access to only their files

• How to share files with clients without Google Drive

• Client handoff that impresses