To stream to Facebook Live with OBS, create or select a live video in Facebook Live Producer, copy the server URL and stream key shown for that broadcast, and enter both in OBS. Use the current details shown in Producer rather than assuming that every account has the same URL or credential options.
RTMPS sends your encoder’s video and audio to Facebook over an encrypted connection. This guide follows the credentials-first workflow, explains OBS settings as documented by OBS, and gives you a way to narrow down dropped frames without treating one preset as right for every connection.
What RTMPS Does
RTMPS is RTMP carried over a TLS-encrypted connection. In practical terms, your encoder connects to a server URL and authenticates with a stream key. The URL identifies the destination; the key acts like a password for that live input. You need both, and they belong in the encoder’s server and key fields respectively.
The encoder packages your video and audio, then sends that stream to the destination. Facebook Live Producer receives the feed and lets you check its preview and status before you publish. This is different from uploading a video file: the encoder sends a continuing signal while it is running, and an interruption can affect what Facebook receives.
OBS’s maintained service configuration lists Facebook Live with an RTMPS default endpoint of rtmps://rtmp-api.facebook.com:443/rtmp/. Treat that as a useful OBS reference, not a substitute for the current URL displayed for your event. If Producer supplies a different URL, use that value. The relevant OBS service configuration is maintained and may change, so check it again if the OBS options look different.
The distinction between an encoder setting and an account setting matters. OBS can document what its Facebook service profile supports, but that does not establish that every Facebook account shows the same controls or accepts every combination. Facebook’s current Live Producer screen is the place to confirm the destination details for your broadcast. For a separate YouTube workflow, planning a 24/7 stream with a cloud streaming service can help you think through the difference between a live encoder session and a file-driven channel, but it is not a Facebook setup guide.
Create a Live Video in Facebook Live Producer
Sign in to Facebook and open Live Producer. Create a live video or select the broadcast you intend to use, then choose the option for streaming software or an encoder if it is offered in your current interface. Labels and available choices can vary, so follow the choices shown to your account rather than relying on screenshots from someone else’s setup.
Before copying anything, make sure the selected destination is the right Page or profile and that the planned broadcast is the one you mean to send. A stream key is not a title, post link, or audience-facing URL. It is the credential OBS uses to send the feed. The audience-facing details, such as the description or scheduled time, are separate from the encoder connection.
Leave Live Producer available while you set up OBS. It is useful to see whether a preview arrives and whether Facebook reports the feed as ready. Do not publish simply because OBS says it is streaming; check the Producer preview and the publishing controls there. If you are scheduling a live video, confirm the intended event and timing in Producer before you begin sending video.
Facebook’s help pages describe going live with streaming software, but the detailed guidance may be behind account sign-in. The Facebook Help Centre’s live-video guidance is a place to check current platform instructions. Do not infer eligibility or account features from the fact that another creator can use a particular option; check what your account currently offers.
Copy the Current Server URL and Stream Key
In the selected Live Producer broadcast, find the streaming-software details. Copy the server URL and stream key currently displayed for that event or account. Depending on the interface, they may be presented together or separately; the important point is to copy the actual values Producer shows rather than typing a remembered endpoint or reusing an old key automatically.
Paste the URL into OBS’s server field and the key into its stream key field. Avoid adding spaces before or after either value. If you use a password manager or temporary note to move the key between applications, remove that note when the setup is complete. Anyone who obtains the key may be able to send a feed to the associated destination, so do not put it in a public document, stream overlay, screenshot, or chat message.
If a connection fails, first compare the fields with the current values in Producer. A previous event may have had different details, and an account may present credential persistence or refresh controls that another account does not. The research available for this guide does not establish universal key-persistence behaviour, so do not count on a key continuing to work across broadcasts. Re-open the current event’s details when unsure.
Keep the Producer page open during first setup. Once OBS is sending, wait for the incoming preview and verify that it shows the expected picture and audio. If the preview is blank, delayed, or absent, do not immediately publish to viewers; confirm the destination and credentials first. For small demonstrations where you are deciding whether to use OBS or another encoder, the software considerations for product demos are a useful comparison of workflows, not a Facebook credential reference.
Configure OBS for Facebook Live
Open OBS Settings and go to the Stream section. If Facebook Live appears in the service list, select it and enter the stream key. If you do not see the service, choose a custom service and supply the current server URL and stream key from Live Producer. Do not choose a YouTube destination or paste Facebook credentials into a profile intended for another platform.
OBS’s Facebook service configuration identifies H.264 video. Use a conservative video setup first, especially if you have not tested the connection at the resolution you intend to publish. OBS lists example combinations of 1280×720 at 30 frames per second up to 4000 kbps and 1920×1080 at 30 frames per second up to 6000 kbps. It also lists profile maxima of 60 fps, 9000 kbps video bitrate, and 128 kbps audio bitrate. These are OBS profile recommendations and limits, not a guarantee that Meta will accept every setting for every account or broadcast.
| OBS profile example | Resolution and frame rate | Video bitrate guidance | When to consider it |
|---|---|---|---|
| Lower starting load | 1280×720 at 30 fps | Up to 4000 kbps | A practical first test where connection stability is uncertain |
| Higher detail | 1920×1080 at 30 fps | Up to 6000 kbps | Use when the upload connection is stable enough to sustain the higher data rate |
These values are ceilings for the cited OBS examples, not mandatory targets. Lowering resolution or bitrate can be more useful than selecting the maximum. A devotional still image with simple motion, for example, may not need the same visual detail as a news loop with small text or a product demonstration where interface labels must remain legible. Test the actual material you intend to stream.
Set audio deliberately as well. OBS’s service profile lists up to 128 kbps for audio, but a higher setting is not automatically better if your connection is already struggling. Listen to the preview and check that the correct audio source is active. A clean feed with understandable speech or music is more useful than an elaborate configuration that drops frames.
When deciding resolution and bitrate, it helps to separate image size from delivery capacity. A higher resolution produces more visual detail, but it also tends to need more data to preserve that detail. The discussion of bitrate needs for a high-resolution YouTube stream is useful background on the relationship, though Facebook’s current requirements should be checked in Live Producer and OBS rather than assumed from a YouTube example.
Protect and Refresh Credentials
Treat the stream key as a credential with access to the live destination. Only enter it into the encoder you intend to use. Do not include it in a tutorial screenshot, public support request, shared spreadsheet, or recording of your desktop. If you need help from someone else, describe the field or error without exposing the key itself.
When your broadcast details change, revisit Live Producer and check what it currently displays. Do not assume the key is permanent, that it is always refreshed in the same way, or that all accounts have the same control for refreshing it. If Facebook provides a refresh or reset action in your interface and you choose to use it, update OBS with the newly displayed value before attempting to send the stream again.
If you suspect the key has been exposed, use Facebook’s current account controls and help guidance to review the credential and destination. Avoid trying random keys or reusing credentials from another event as a workaround. The Meta Business Help Centre is another official place to check for current live-video instructions, though sign-in may be required to see account-specific details.
Credential checks also make troubleshooting more efficient. When OBS cannot connect, verify the current destination and key before changing unrelated encoding settings. If the values are correct but the feed still does not appear, then examine the network connection, selected OBS service, firewall or network restrictions, and whether the right Producer event is open. Change one variable at a time so you can tell which change helped.
Diagnose Dropped Frames
In OBS, watch the dropped-frames counter and connection indicator while sending the stream. OBS’s guidance associates a rising dropped-frames counter and a yellow or red connection square with an unstable service connection or a bitrate the connection cannot sustain. That points first to the path between your encoder and the service, not necessarily to a problem with the video file or a Facebook setting.
Start with the least disruptive checks. If you are on Wi-Fi, test a more consistent connection if available, and pause other activities that may be using the upload path. Check whether the problem appears continuously or only when another device or application is active. A speed test can offer a snapshot, but it does not prove that the connection will remain stable throughout a live broadcast.
Next, reduce the bitrate and test again. If you started at 1920×1080 and 6000 kbps, for example, try the OBS example of 1280×720 at 30 fps with a lower bitrate within its 4000 kbps guidance. If the counter settles, the original combination may have exceeded what your current connection could sustain. Keep enough image clarity for your content: small on-screen text can become difficult to read if you lower quality too far.
If the counter continues to rise, reduce the load again or check the connection by another route. Avoid increasing bitrate just because the picture looks soft; that can worsen congestion. For a long-running YouTube channel, advice on dropped frames over Airtel broadband describes useful connection-first thinking, but its platform context is YouTube, not Facebook. Treat it as general network troubleshooting rather than a Facebook-specific fix.
A connection error without dropped frames calls for a different first check. Re-copy the current URL and key from the selected Live Producer event, confirm that the server and key are in the right OBS fields, and ensure OBS is set to Facebook Live or the correct custom service. The sources checked for this article do not establish a complete current Facebook error-code guide, so avoid assigning a precise meaning to an error message without checking Facebook’s current help material.
Once the feed arrives, watch the preview and status in Producer before publishing. Check picture, sound, and the intended event. If the preview is stable but OBS continues to report dropped frames, do not assume the issue is resolved simply because the audience view looks acceptable at that moment; continue monitoring and use a bitrate your connection can sustain over the length of the broadcast.
If your actual goal is an always-on YouTube channel rather than a broadcast, keep the platform distinction clear. StreamNeo turns an uploaded file into a YouTube live stream, which can remove the need to leave your own computer running for that specific YouTube workflow; it does not stream to , and setup remains separate.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Do I always use the same Facebook server URL?
No. OBS lists a default Facebook RTMPS endpoint, but use the URL currently shown in your Live Producer broadcast if it differs. Account and event interfaces can vary, so check the active event rather than relying on a value copied from an old setup.
Can I reuse my stream key for another broadcast?
Do not assume that you can. Key persistence and refresh options may differ by account or event, and the available research does not establish one universal behaviour. Check the current Live Producer details and use the credential shown for the broadcast you are configuring.
Why does OBS show dropped frames?
OBS associates a rising dropped-frames counter and a yellow or red connection indicator with an unstable connection or a bitrate that the connection cannot sustain. Check connection consistency and try a lower bitrate before raising it or changing unrelated settings.
Does StreamNeo send this stream to ?
No. StreamNeo is for turning an uploaded video into a 24/7 YouTube live stream. Configure Live separately in Live Producer and OBS using ’s current destination details.