Instagram Live Producer RTMP Runbook for StreamableRun Cloud OBS

The direct answer

Instagram Live Producer is useful when a creator wants a real encoder workflow instead of only going live from the Instagram mobile app. Instagram's official Live Producer announcement says streaming software can send to Instagram Live by adding Instagram as a Custom RTMP destination with a stream URL and stream key. Current encoder guides from Magewell and PRISM still describe the same basic shape: professional account, desktop Live Producer page, stream URL, stream key, encoder output, Instagram preview, then Go Live from Instagram.

For StreamableRun operators, the important part is not the first setup screen. The important part is the handoff. Instagram keys are session-like, vertical framing matters, the browser Live Producer page needs to stay open in common workflows, and Instagram is usually one destination beside Twitch, Kick, YouTube, or a private monitor. Treat Instagram as a destination with its own preflight, not as the whole production system.

The clean setup is source to StreamableRun ingest, Cloud Hosted OBS for the vertical-safe program, Instagram Live Producer as a custom RTMP-style destination, and a producer checklist for preview, Go Live, monitoring, and end-of-stream. Do not make the streamer paste keys into a phone while the show is already live.

What matters now

Instagram Live Producer is old enough that many streamers have heard of it, but it is still easy to operate badly. The current docs from encoder vendors keep repeating the parts that matter: use a professional Instagram account, open Live Video from Instagram on desktop, copy the stream URL and stream key, keep the Live Producer window open, send the encoder feed, verify preview, then click Go Live in Instagram.

PRISM's guide says Instagram does not provide a static stream key, and that the stream key expires if the live stream ends or the Live Producer window closes. Magewell's guide similarly notes that the stream key resets with every stream. That means Instagram should not be treated like a permanent Twitch or YouTube destination that never changes.

This is where Cloud OBS helps. You can build the real show once in StreamableRun, then update the Instagram destination key for that session. The producer owns the key update and preview check. The streamer owns the content. Nobody should be rebuilding scenes, changing audio routing, or pasting destination secrets from the field during the first live minute.

• Professional Instagram account is part of the desktop Live Producer workflow.
• Stream URL and stream key are copied from Instagram's Live Producer page.
• Keys should be treated as per-stream credentials, not permanent destination settings.
• Instagram preview and Go Live happen on the Instagram side, not only in OBS.
• Cloud OBS should already have vertical scenes and fallback ready before the key is pasted.

Use the exact URL Instagram gives you

Do not force a protocol from memory. Instagram Live Producer gives the stream URL and stream key for the current live setup. Add that URL exactly as provided into StreamableRun or your encoder's custom RTMP destination field. If the URL starts with RTMP, use that. If Instagram changes behavior in the future, use the current Live Producer output and update the runbook.

This matters because streamers often mix platform assumptions. YouTube has its own RTMPS documentation. Twitch and Kick have their own server and key models. Instagram Live Producer has its own session flow. A producer who pastes a stale Instagram key into a reused destination may see a clean Cloud OBS preview and still have no Instagram Live.

Use one destination owner. That person opens Instagram on desktop, creates the live, copies the current URL and key, updates StreamableRun, starts the Cloud OBS output, verifies the Instagram preview, clicks Go Live, watches chat or appoints someone to do it, and ends the Instagram session correctly. Splitting those steps across three people is how session keys get lost.

• Copy the Stream URL and Stream Key from the current Instagram Live Producer session.
• Do not reuse last stream's Instagram key.
• Do not close the Live Producer page during setup unless you are ready to regenerate the session.
• Name the destination by date or show, such as Instagram Live 2026-07-11.
• Remove or rotate stale keys after the stream so nobody trusts them later.

Build the vertical scene first

Instagram is phone-native. A horizontal scene sent into Instagram can look cramped, cropped, or hard to read. PRISM's guide specifically tells users to use a vertical aspect ratio for Instagram, with 1080x1920 as the example shape. That does not mean every element in your StreamableRun show needs to be vertical, but the Instagram destination should receive a layout built for vertical viewing.

Start with the subject. Keep the host or field action in the vertical-safe center. Move chat, captions, alerts, and sponsor graphics to phone-readable positions. Do not put critical text at the far left or right edges of a horizontal master scene and then ask Instagram to deal with it.

If the same show also goes to Twitch or YouTube horizontally, build separate Cloud OBS scenes or separate output layouts. One camera can feed both, but the composition should not be an accident. The producer should know which scene is for Instagram and which scene is for the horizontal destinations.

• Create Instagram Main, Instagram BRB, Instagram Slate, and Instagram Safe Cut scenes.
• Test long usernames, captions, paid alerts, and sponsor text inside the vertical frame.
• Use bigger text than a desktop Twitch overlay would need.
• Keep the fallback scene vertical too, not only the main camera scene.
• Check Instagram preview from a phone before calling the layout ready.

Preflight order

Instagram Live Producer has a two-sided start. Your encoder can send video, but Instagram still needs preview and Go Live from the Live Producer page. That makes preflight order important. If the producer starts output too early, they may burn time while people are still editing title and destination details. If they click Go Live before checking the Cloud OBS scene, the audience sees the rehearsal.

Use a fixed order. Build the Cloud OBS vertical scene. Start the StreamableRun server. Open Instagram Live Producer. Create the live session and title. Copy the current URL and key into the Instagram destination. Send a holding scene first. Confirm preview on Instagram. Confirm audio. Then click Go Live in Instagram. Only after that should the producer cut from holding to the real source.

That order keeps the first public frame controlled. If the source is still connecting, viewers see a holding scene. If audio is wrong, the producer catches it before the main scene. If the Instagram key is wrong, the team fixes destination setup without exposing the streamer fumbling with menus.

• Prepare vertical Cloud OBS scenes before opening the public Instagram live.
• Copy fresh Instagram URL and key for this session only.
• Start with a holding scene, not the live camera.
• Verify Instagram preview and audio before pressing Go Live.
• Cut to the main scene only after the producer sees the public state.

Monitoring and chat

Instagram monitoring is different from Twitch or YouTube monitoring. The Live Producer page may be where the producer sees preview, chat, notifications, and the final Go Live control. PRISM's guide warns that preview can be delayed, and Magewell tells users to keep the browser window open to view chat and notifications. That means Instagram needs a dedicated screen in the control room.

Do not let the same person watch all platforms silently. If Instagram is important, assign an Instagram destination owner. That person watches Live Producer, public phone playback if available, chat, title, and session end. The Cloud OBS producer should stay focused on scenes, source health, audio, and cross-platform destination state.

If the team is multistreaming, write down which platform wins when layouts disagree. A vertical Instagram issue should not force the Twitch horizontal output to change unless the root cause is shared. A Twitch title problem should not distract the Instagram owner while the Instagram preview is still waiting to go live.

• Keep Instagram Live Producer open on a dedicated producer or destination-owner screen.
• Use a phone check for audience-side vertical framing when possible.
• Separate Instagram chat/moderation from Cloud OBS scene operation.
• Log whether a problem is source, Cloud OBS, Instagram destination, or public playback.
• End the Instagram live from the proper Instagram control, then stop the encoder output.

StreamableRun setup path

Start with a normal StreamableRun source path: phone app, local OBS, camera, hardware encoder, LiveU, or shared ingest. Build Cloud Hosted OBS scenes for Instagram Main, Instagram Holding, Instagram BRB, Instagram Technical Slate, and Instagram End Card. Keep the show source separate from the Instagram destination credential.

Add Instagram as a custom destination using the current Live Producer stream URL and stream key. Send the holding scene first. Confirm preview. Confirm audio. Click Go Live in Instagram. Then cut to the real source. If the source drops, keep the Instagram live session active and cut to fallback in Cloud OBS while the source reconnects.

StreamableRun is the best default place for this workflow because Instagram's session key can change while the production layer stays stable. The streamer does not need to rebuild OBS. The producer updates one destination, monitors the preview, and keeps the public show recoverable.

• Source to StreamableRun ingest.
• Cloud OBS vertical scene collection for Instagram.
• Fresh Instagram Live Producer URL and key entered as the destination for this session.
• Holding scene sent before Go Live.
• Fallback scene and destination owner ready for source loss or key mistakes.

Other resources

Use these pages to verify the current Instagram Live Producer flow, professional account requirements, RTMP key behavior, vertical output expectations, and StreamableRun production features before using Instagram as a live destination.