Facebook Reels Uploader

facebook-reel-upload

Charged once per Reel confirmed published through the Facebook composer. A run that publishes nothing is never charged this fee — but it is still charged for the bandwidth it moved before it stopped, under "Video megabyte (metered exit only)".

facebook-reel-upload-api

Charged once per Reel confirmed published through Meta’s official Graph API. Cheaper than the browser lane because no residential bandwidth is used. A run that publishes nothing is never charged this fee, and the Graph API lane is never charged per megabyte.

video-megabyte

Charged only on browser runs that used this Actor’s metered residential connection, and charged on a confirmed publish and on a failed run alike, because that bandwidth is paid for either way. On a confirmed publish it is one event per megabyte of your video — the file that crossed that connection on its way to Facebook. On a run that stopped early it is the traffic actually measured across that connection, plus whatever of your file had already been pulled in from your host; that part is charged at what those bytes cost rather than at the per-megabyte rate, so on a small download it often rounds to nothing. Measured bytes only, never an estimate — a leg that cannot be measured is charged as zero. Never more than a successful publish of the same file would have cost, and never past the "maxTotalChargeUsd" you set. Runs on your own proxy servers, on a non-residential group, with the Apify proxy switched off, or on the Graph API lane are never charged this.