How to upload creatives to the media library
Last updated June 10, 2026
Your media library is the shared pool of images and videos you reuse across launches. You add to it from the Creatives step of the bulk launch wizard, where a drop-zone lets you bring files straight from your computer into uplads. This guide walks through formats, the size limit, progress tracking, and why uploads keep running even if you move on.
If you'd rather pull files in from cloud storage, see import creatives from Dropbox or import creatives from Google Drive instead.
Supported formats and the 250 MB size limit
The uploader accepts standard ad-ready formats:
- Images — JPG, PNG, and WebP
- Videos — MP4, MOV, and WebM
Each file can be up to 250 MB. The file picker is filtered to these types, so unsupported files won't show up when you browse, and dropping the wrong type is safely ignored. For larger videos, the uploader automatically switches to a chunked (multipart) upload behind the scenes, so big files transfer reliably without you doing anything differently.
When a file is added, uplads reads its pixel dimensions client-side before uploading. That's what powers automatic placement detection and naming field auto-detection later in the wizard.
Drag-and-drop or click to browse the drop-zone
You'll find the drop-zone at the top of the Creatives step. There are two ways to add files:
- Drag and drop — drag one or more files from your desktop onto the drop-zone. It highlights while you're hovering, so you know it's ready to receive the drop.
- Click to browse — select the Select files button (or click the drop-zone) to open your system file picker. You can multi-select to add a whole batch at once.
Both paths add files to the same upload queue, so you can mix dragging and browsing in one session.
Watching real-time progress in the collapsible list
Once files start uploading, a summary bar appears just below the drop-zone. It stays compact by default so it doesn't push the media library off-screen, while still showing you everything that matters:
- A count of how many files have uploaded and how many are still uploading
- An overall percentage, weighted by file size, so a large half-finished video is counted fairly against a tiny finished image
- A progress fill that sweeps across the bar left-to-right as the batch completes
Click the summary bar to expand it and see a per-file list. Each row shows the file name and its live status — Queued, Preparing…, an uploading percentage, or Finalizing… — so you can tell exactly where each file is in the pipeline.
Cancelling an in-flight upload or retrying a failed one
You stay in control of every file in the queue:
- Cancel — expand the list and click the X on any row to stop an upload that's still in progress. It's removed from the active queue immediately.
- Retry — if a file fails, it appears in a red error row with the reason shown inline. Click Retry to re-attempt that single file without re-adding the whole batch.
If a file keeps failing, see how to fix creative upload failures for common causes and fixes.
Continuing to the next step while uploads run in the background
You don't have to wait for uploads to finish before moving forward. The summary bar reminds you: you can move to the next step — uploads keep running. Advance to targeting or any later step in the launch wizard and your files keep transferring in the background. Each one drops into the media library and becomes selectable the moment it finishes.
Why uploads persist across navigation and refresh
uplads runs the upload engine at the app level rather than inside a single page, so your transfers survive moving around the product:
- Navigate away and back — when you return to the Creatives step, the progress list re-populates from the still-running queue instead of resetting to empty. The account-wide upload dock also keeps everything visible no matter where you are.
- Accidental refresh — a lightweight snapshot of each in-flight job (name, size, status, percent) is stored in your browser, so after a reload uplads can tell you which uploads were in progress rather than silently losing track of them.
This is the same resilience that powers auto-saving and resuming drafts — your work in progress is never thrown away just because you clicked the wrong thing.