Skip to main content

Uploading a new file or working asset to a project

You can add new files or working assets to a project directly from the project detail page. This article covers uploading files and what happens to them afterward.

Opening the upload dialog​

From a project's Assets tab, click Upload Asset (or drag files directly onto the page). The Upload assets dialog opens; any settings you choose apply to every file in the batch.

Choosing what you're uploading​

  • Working file vs Proof — toggle at the top. Working files are for internal reference; proofs go through your workflow for review and approval.
  • Source — pick one:
    • Upload files — browse or drag files in (locked once your workspace's storage limit is reached).
    • URL / Weblink — paste a link (Figma, YouTube, a webpage, a PDF URL, etc.), optionally test that it's reachable, then add it to the batch.
    • Record screen — capture your screen directly in-app, preview it, and add it to the queue.
    • Canvas — open an infinite canvas for freehand sketching; it autosaves as you draw.
    • OneDrive and Google Drive — browse an existing connected account's documents or create a new one.

Executable files are always blocked, and oversized files (over your workspace's per-file limit) are flagged and excluded from the batch.

Destination​

On the right side of the dialog:

  • Select project — search for and pick the project this batch belongs to. If you opened the dialog from inside a project, it's pre-selected.
  • Select workflow — only shown when uploading outside of a project context; inside a project, proofs pick up the project's default proof workflow automatically.

Each file in the batch can be renamed before it finishes uploading, and shows its own upload progress.

After upload​

Files are staged, then committed once every file in the batch has finished uploading — this is the same for both single files and multi-file batches. Uploading a new version of an existing asset (rather than a brand-new file) is a separate flow — see Uploading and managing proof versions.