Upload the video, paste the stream key from Facebook Live Producer, and Streamza broadcasts it to your Page, profile or group as a real live video — with live reactions, comments and follower notifications. No OBS, no encoder, no machine left running.
| Setting | Value |
|---|---|
| Server URL | rtmps://live-api-s.facebook.com:443/rtmp/ |
| Stream key | From Live Producer → Streaming software |
| Protocol | RTMPS — Facebook requires the encrypted variant |
| Video codec | H.264 |
| Audio codec | AAC |
| Keyframe interval | 2 seconds |
| Maximum broadcast length | 8 hours per live session |
Streamza fills the RTMPS server URL in for you when you choose Facebook, so you only paste the key. Note the trailing slash — a URL missing it is one of the most common causes of a connection that silently fails.
Go to facebook.com/live/producer, or on a Page use Create post → Live video. Choose Go live, then select Streaming software as the source rather than the camera.
Select the Page, profile, group or event, write the title and description, then copy the stream key. Tick persistent stream key if you want the same key to keep working for future broadcasts.
At streamza.live/studio, claim a free slot, upload your MP4 and select Facebook so the RTMPS URL fills in. Paste the key.
Press start in Streamza and wait for the preview to appear in Live Producer. Once you can see your video there, click Go live. You can then close everything.
Two Facebook timers to know about. After your encoder starts sending, you have a limited window — around four hours — to actually click "Go live" before the session is discarded. And once live, a single broadcast is capped at 8 hours, after which Facebook ends it automatically.
Not as one unbroken broadcast. The 8-hour ceiling is a hard platform limit, so a permanently live Facebook channel would mean starting a fresh broadcast at least three times a day — a new post and a new comment thread each time.
Facebook is also the strictest major platform about looping content. Repetitive or unattended broadcasts that add nothing new get limited reach or removed, and Pages that do it repeatedly can lose live access altogether.
Practical advice: use Facebook for scheduled pre-recorded broadcasts — the edited service, the weekly show, the product launch — and put genuine always-on channels on YouTube, which is built for them. If you want both, multistream the same upload to Facebook for the 8-hour window and let YouTube carry the round-the-clock loop.
| Destination | Worth knowing |
|---|---|
| Page | The normal choice for businesses and creators. Gives you insights, scheduling and a persistent key. |
| Personal profile | Works fine, but reach is limited to friends and followers, and there are fewer analytics. |
| Group | Good for communities and classes. You need permission to post live in that group. |
| Event | Streams into the event page so attendees get notified. Ideal for a pre-recorded session that runs at a set time. |
Almost always the key or URL. Re-copy the key, confirm the server URL ends with /rtmp/, and make sure nothing was truncated on paste.
Facebook has not received video yet. Give it a few seconds after starting the stream in Web Studio; if it is still greyed out after a minute, the connection is not arriving.
You hit the 8-hour limit, or Facebook expired the session because too long passed between the encoder connecting and you clicking "Go live".
Single-use keys are only valid for the broadcast they were generated for. Enable a persistent stream key on the Page if you stream regularly.
Facebook down-ranks repetitive live content. Vary what you broadcast, and do not loop the same file on Facebook indefinitely.
Yes. Choose "Streaming software" as the source in Live Producer and Facebook accepts an RTMPS feed — it does not care whether the frames come from a camera or a file. Your own recorded content is fine; other people's is not.
Eight hours per broadcast. Facebook ends the session automatically at that point, so a continuous channel needs a fresh broadcast several times a day.
Both work. A Page is better for anything public-facing — you get insights, scheduling and a persistent stream key that saves re-copying it every time.
Facebook requires the encrypted variant of RTMP for all ingest. Streamza sends RTMPS to Facebook automatically, so there is nothing to configure.
Yes, up to three destinations at once on the Multistream plan, from a single upload. See multistreaming.
Yes. Facebook saves the completed broadcast as a video post, so it keeps collecting views, comments and shares afterwards.
No. The broadcast runs on Streamza's servers once started, so you can close the browser and shut your device down.
Upload, paste your key, go live. Free to try, no account needed.
