Instagram Reel Uploader

Instagram Reel Uploader

Posts a Reel to your own Instagram account from a URL. You give it the video, a caption, and your own exported session cookies, and it drives a headless browser through Instagram's web composer to publish the Reel. It's built to be the publish step of a faceless-content or scheduling pipeline.

How it works

It downloads your video, launches a headless Chromium routed through your proxy, loads your exported Instagram cookies into the session, opens the Create composer on instagram.com, sets the file, advances through the crop and edit steps, writes the caption, and shares. There is no shared login. You bring your own session each run, exported from a browser where you're already signed in.

Try it with no login (demo / sample mode)

Run it with no cookies (or set demoMode: true) and it returns one clearly-labeled sample row and uploads nothing — a try-before-you-export preview. The sample row carries _demo: true and a _notice explaining that no credentials were supplied. To post for real, supply your own session (below).

Input

How to export your Instagram cookies

1. Log in to instagram.com in Chrome/Edge. 2. Install the Cookie-Editor extension and open it on the Instagram tab. 3. Click Export → Export as JSON (this copies a cookies array including sessionid and ds_user_id). 4. Paste that JSON into the cookies field. It is automating your own logged-in session — nothing is shared.

Output

Exactly one dataset record per run, always.

• Demo run: { _demo: true, _sample: true, _notice, ok: true, demo: true, charged: false, reelUrl: ".../reel/SAMPLE/", ... } — nothing uploaded.
• Real success: { ok: true, charged: true, platform, caption, posted: true, confirmed: true, reelUrl, finalUrl } — confirmed is only true after Instagram's "has been shared" confirmation is actually seen, and reelUrl is the real permalink when it can be read.
• Anything else: { ok: false, charged: false, errorCode, error, reason, hint } — a diagnostic row naming what went wrong and what to do about it, plus a debug screenshot + page HTML saved in the run's key-value store and named in the row.

A run that cannot post does not fail — it returns the diagnostic row and ends as SUCCEEDED. A failed run and a succeeded run cost you the same platform start fee, so crashing would charge you the same and tell you less. The instagram-upload charge fires only on the confirmed-success path.

Error codes

Method & reliability

This is a best-effort browser-automation method: it drives Instagram's real web "Create" composer (there is no official Reels upload API for personal accounts). It checks your session is logged in before downloading your video, selects Reel where offered, advances through the crop/cover/edit steps with explicit waits and several fallback selectors per step, verifies the file registered and the caption took, then watches for either Instagram's "has been shared" confirmation or an explicit refusal for up to 3 minutes.

Because it depends on Instagram's live UI, a layout change on their side can break a step. When that happens you get a LAYOUT_CHANGED row and a screenshot, not a silent wrong result and not a charge.

Example

{
  "videoUrl": "https://cdn.example.com/reel.mp4",
  "caption": "behind the scenes #reels",
  "cookies": "[{\"name\":\"sessionid\",\"value\":\"...\",\"domain\":\".instagram.com\",\"path\":\"/\"}]"
}

Pricing

$0.35 per successful upload, plus a $0.000025 run-start fee — the start fee is billed once per GB of run memory, so at the default 2 GB a run start costs $0.00005.

This price takes effect on 31 August 2026. Runs before that date still bill the previous $0.10 per successful upload; runs from 31 August 2026 onward bill $0.35. The run-start fee is unchanged.

The upload charge fires only after Instagram confirms the Reel is live. Any run that ends in ok: false — bad input, dead cookies, a checkpoint, an action block, an unconfirmed share — pays the start fee and nothing else. Demo/sample runs are not charged for an upload either.

Proxy bandwidth is not billed to you. The Actor routes through its own residential connection and absorbs that cost. That absorbed bandwidth is what the 31 August 2026 rate covers, and it is also why a video sent over it is capped at 100 MB — a Reel is normally well under that. If you need the full 600 MB allowance, put your own proxy servers in proxyConfiguration.proxyUrls; they are used exactly as given and the cap lifts.

FAQ

Is there an official Instagram Reels upload API? No. Meta's Content Publishing API only covers Instagram Business and Creator accounts connected to a Facebook Page, and it needs an app review. This Actor drives the normal instagram.com web composer with your own logged-in session instead, so it works with a personal account.

Do you get my Instagram password? No. You paste session cookies, not credentials, and the field is stored as a secret. Log out of that Instagram session to revoke them.

Why did my run come back with SESSION_INVALID? Instagram session cookies expire, and they are also invalidated when you log out or change your password. Re-export them with Cookie-Editor from a tab where you are signed in.

Will I be charged if the Reel does not post? No. The instagram-upload event ($0.10 until 31 August 2026, $0.35 from that date) fires only after Instagram's own "has been shared" confirmation. Everything else returns an uncharged diagnostic row.

Can it post to a Story, a carousel, or a feed photo? No. Reels only, one video per run.

Why does it need a proxy? Instagram treats a datacenter address logging into your account as suspicious, so the Actor routes through a residential connection by default and pays for that bandwidth itself. You do not need to configure anything. Choosing a different proxy group in the input has no effect; supplying your own servers in proxyUrls, or turning the proxy off entirely, does.

What this does not do

• It does not create or find your video. You host the .mp4 and pass a public https URL.
• It does not schedule. One run posts one Reel, immediately.
• It does not manage multiple accounts in one run. One session, one Reel.
• It cannot clear a checkpoint or an action block for you. Those need a real browser on the account.
• It does not guarantee delivery when Instagram changes its composer. That is reported as LAYOUT_CHANGED with a screenshot, never as a silent success.

Notes

This automates your logged-in Instagram session, which Meta's terms discourage, so run it on your own account at your own discretion. Automating a session from a new device/IP is a pattern Instagram may flag with a temporary action-block or checkpoint — a residential proxy in your own country reduces (but does not eliminate) this. Cookies expire, so re-export them when you see a "not logged in" error. Because it drives Instagram's actual web UI, a layout change on their side can break a selector and need an update — failures are surfaced clearly with a saved screenshot, never as a silent success.