File storage for freelancers: deliverables, handoffs and keeping clients separate

A freelancer’s files are the business. There is no IT department, no shared server, no colleague who kept a copy. If a client asks for the final version of something from eighteen months ago and you cannot find it, that is a problem with your name on it.

The good news is that a freelancer’s needs are simple and repetitive, which means a simple system covers almost everything. This article lays one out: how to organise client work, how to hand over deliverables cleanly, how to keep clients from seeing each other’s files, and how to close a project so it stays findable for years.

One folder per client, identical inside

The foundation is a Clients folder with one subfolder per client, and the same three folders inside every one of them:

• Working: everything in progress. Drafts, source files, notes, references.
• Delivered: what you actually sent, named with the date you sent it.
• Admin: the contract, the brief, invoices, and any correspondence worth keeping.

The sameness is the feature. You never have to decide where something goes, and when you open a client folder you have not touched for a year, you know exactly where to look.

Keep your own business files out of Clients entirely. A separate Business folder holds your finances, templates, contracts and marketing. Mixing your tax return in with a client’s assets is how the wrong file gets shared.

Naming deliverables

A deliverable’s file name should tell the client, and you, what it is without opening it:

2026-10-09 Acme homepage copy v3.docx

Date first in year-month-day, then the client or project, then what it is, then the version. When the client approves v3, you can rename a copy with final in place of the version if you like, but keep v3 in Delivered as well. Clients have a way of asking for “the version before the final one”.

Handing over deliverables

The handoff is the moment a freelancer is most exposed. Email attachments are the usual method and they have real problems: size limits, files that bounce, and a client inbox with four versions of the same thing and no way to tell which is current.

A share link does this better. The process:

1. Put the final file in the client’s Delivered folder.
2. Create a share link on that file, or on a dated subfolder if there are several.
3. Set an expiry date. Two to four weeks is enough for a client to download and check; if they need it again later, you make a new link, which is also a natural moment to confirm they still should have access.
4. Leave downloading on; this is a delivery.
5. Send the link with a short note.

For review rounds before the final, the same process with downloading switched off works well. The client views the draft in the browser and sends notes; they do not end up with a copy of a half-finished piece sitting in their downloads. Previews work for the common deliverable types, including PDFs, Office documents, images and MP4 or MOV video, so the client does not need the software you made it in.

For anything confidential, add a password and send it separately. Password-protected and expiring links covers the detail.

When a client needs ongoing access

Some clients are not one-off. A retainer client who needs to drop source material in every month, or pull previous work whenever they like, is better served by sharing a folder with them by email than by a stream of links.

Share the client’s own folder, or a subfolder of it, with view permission if they only need to fetch things and edit permission if they need to add. Because it is tied to their account rather than a URL, they cannot forward the access, you can see that they have it, and you can remove it the day the retainer ends. Share links vs sharing with a person explains when each method fits.

If you work with a client’s whole team, or they want to work alongside you, a workspace for that client is cleaner still. You can be the owner, the client’s people can be contributors or editors, and the files remain in one place regardless of who comes and goes. Onlinedrive includes workspaces from the Professional plan; see Workspaces for small teams.

Keeping clients separate

The nightmare scenario is a client seeing another client’s files. It happens most often in one of three ways, and all three are preventable.

Sharing a parent folder. If you share Clients or your whole drive, everything underneath is exposed. Only ever share from inside a specific client’s folder, never above it.

Reusing a link. A link made for client A, pasted by mistake into an email to client B. Make a fresh link for each delivery and let old ones expire. If a link is still live when you spot the error, delete it; the link stops working immediately.

Mixed folders. A Current work folder with three clients’ drafts in it is an accident waiting to happen. Work inside the client’s own Working folder from the start, even for a quick job.

If you handle particularly sensitive clients, or clients in different countries with different data rules, you can go a step further and keep them in separate drive accounts in different regions. A UK freelancer with EU clients might keep a London drive and a Frankfurt drive. It is more than most need, but it makes the separation structural rather than a matter of care. Why the region your files live in matters covers the thinking.

Collecting files from clients

Clients send things in whatever way is easiest for them, which usually means email attachments, chat messages and occasionally a USB stick. Get them into the client’s Working folder as soon as they arrive. The thirty seconds it takes is repaid the first time you need a logo file that was in a message thread from four months ago.

For clients who send a lot, share a From client subfolder with them by email with edit permission, so they can drop files in directly. Many are relieved to have one place to put things.

Closing a project

When the work is delivered, paid and the client has confirmed they have everything:

1. Make sure the final deliverables are in Delivered with dates.
2. Make sure the signed contract and final invoice are in Admin.
3. Delete any share links that are still live, or confirm they have expired.
4. Move the whole client folder to Archive / Clients / Client name if you do not expect further work. If you do, leave it where it is.

The archived folder is still searchable and still a click away. Two years later, when the client asks for the files because they lost them, you find them in a minute, make a link, and look like exactly the kind of professional they should hire again.

Backing it all up

Your clients’ work being in the cloud is one copy. It is not the only one you should have. Keep a local copy of active projects on your machine, and an external drive copy of everything, and you have a proper 3-2-1 backup. A freelancer who loses a client’s files has usually lost the client too.

Storage size

Freelancers’ needs vary enormously by discipline. A copywriter can run a decade of work in a few gigabytes. A photographer or video editor can fill 500 GB in a year with deliverables alone. Decide based on what you deliver, not what you shoot; raw material belongs on local drives. The plans at /pricing run from 250 GB upwards, with annual or lifetime payment, and lifetime is worth a look if your archive is something you intend to keep. Lifetime vs annual cloud storage weighs it up.

Next step

Create Clients, Business and Archive. Inside Clients, make a folder for your most active client with Working, Delivered and Admin inside it, and move that client’s current files in. Do the next client tomorrow. In a week, every active client is in the system, and the next deliverable goes out as a dated file with an expiring link.