Files live on the project
The engagement gives every file its context — which client, which work, and when it arrived.
What you can do with project files
Upload files
Add deliverables and payment proofs to the project they belong to.
Download & remove
Retrieve a file whenever you need it, and remove it when it’s no longer relevant.
See the details
Each file shows its name, size, type and when it was added, with a category to sort by.
Kept on the project
Files sit alongside the milestones, invoices and history for the same engagement.
Supported types include PDF, Word, Excel, PNG, JPG and ZIP, up to 20 MB each.
Outside the engagement vs. on the project
When a file lives outside the engagement
- The folder name is the only context
- Project details live somewhere else
- A client update means gathering files and status
- Deliverables and payment proofs get mixed
- The project history doesn’t show the file
When the file stays on the project
- It belongs to a specific engagement
- It’s clear why the file is there
- The upload is recorded in activity
- The read-only view can surface it to the client
- It sits alongside milestones and invoices
Files and project history
Uploading and removing a file are recorded in the project’s activity history, so you can see when a deliverable was added without keeping notes elsewhere.
What the client sees
The read-only project link lists the project’s files, where the client can view and download them without an account. Uploading stays with you — the shared view doesn’t accept client uploads.
Project context rather than another storage platform
Remex keeps files with the client work they belong to. It isn’t a full cloud-storage or collaboration platform, and it doesn’t try to replace one — there are no folders, versions or in-app editing. The point is that a file stays connected to its engagement.
What you stop searching for
Instead of: Wondering which folder holds the final deliverable
You can: Open the project and find its attached files
Instead of: Reconstructing when a file was added
You can: Check the upload entry in the project activity history
Instead of: Sending project status and files separately
You can: Share the read-only project link that shows both
Files are part of the engagement
They belong to a project, which belongs to a client — so a deliverable always has a home.
Who this is for
Freelancers who hand over deliverables and keep payment proofs, and want each file to stay with the project it came from rather than in a separate drive.
Questions about project files
Can I upload files to a project?
Yes. Files are uploaded to a specific project, so they stay attached to that engagement.
Can I download project files?
Yes. You can download any file on the project when you need it.
Can I delete a file?
Yes. You can remove a file from the project when it’s no longer needed.
Which file types are supported?
PDF, Word (DOCX), Excel (XLSX), PNG and JPG images, and ZIP archives.
Is there a file-size limit?
Yes. Each file can be up to 20 MB.
Can my client see project files?
Yes. Files on a project appear in the read-only project link you share, where the client can view and download them.
Does the client need an account?
No. The shared project view opens through a link, without the client creating an account.
Can clients upload files?
No. The shared view is read-only — clients can view and download, but uploading is done by you.
Does Remex keep file versions?
No. There is no version history; a file is uploaded, downloaded or removed as a single item.
Are file actions shown in project history?
Yes. Uploading and removing files are recorded in the project’s activity history.
Is Remex a replacement for Google Drive or Dropbox?
No. Remex keeps files attached to the project they belong to. It isn’t a full cloud-storage or collaboration platform — the value is the connection to the work.
Keep the work, files and project history together
Upload to the project, and the file stays where the work is.