What an upload run does now
In Metricool (Drive + CSV): every rendered file is uploaded to Drive and
shared by link, the Metricool bulk-upload CSV gets a row with that link and the
texts, and the log ends with the CSV path (plus its safe-to-open
…_review.xlsx twin). Import the CSV in Metricool's planner — done. Cover
frames ride along as thumbnail links; first comments are included where
Metricool publishes them.
In Metricool API: there is no CSV. Each file goes to Drive, Metricool re-hosts it from that link, the Drive copy is deleted right afterwards, and the post appears in Metricool's planner scheduled for its slot. No cover frame is sent in this mode — the API has no documented field for one.
| Metricool (Drive + CSV) | Metricool API | |
|---|---|---|
| Where the post lands | in the CSV you import | in the planner, scheduled |
| The Drive copy | stays until you delete it | deleted after the re-host |
| Cover frame | shipped as a thumbnail link | not sent |
Drive stays a transfer vehicle, not a library
Metricool copies the media onto its own servers — at re-host in the API mode, at import in the CSV mode — so a Drive copy is dead weight the moment that happened. The API mode removes its copy for you; CSV-mode files stay until you delete them under Settings → Storage → Google Drive uploads, which lists the app's own files with their status and frees the space at once.
If the Drive is full, the run stops with one plain-language message (with the numbers) instead of failing every post the same way, and pre-flight warns beforehand when a batch doesn't fit the free space.