A custom RTMP destination lets you send an encoder’s live output to a platform or service by entering the server URL and stream key it provides. The destination supplies those details; there is no universal URL or encoder configuration, and many platforms offer a built-in account connection that avoids manual entry.
The dependable sequence is to confirm the destination supports encoder feeds, copy its current endpoint details, enter them in the matching fields, save, start the broadcast and check reception on the destination platform. Menus and requirements vary, so use that platform’s current instructions rather than copying another service’s settings.
What a custom RTMP destination is
RTMP is a protocol used to send live audio and video from an encoder to a receiving service. A custom destination is the manual connection path: the service gives you a server URL and a stream key, and you enter both into the software that is producing the stream. The encoder sends the feed to the specified endpoint, while the destination platform makes it available through its own live-video workflow.
The server URL identifies where the feed should be sent. The stream key identifies the particular live destination or publishing session to which it belongs. Both are destination-specific credentials. A URL from one platform may not work on another, and a key issued for one event or channel should not be assumed to work for a different one. Check the destination’s current instructions whenever you create a new live session or change platforms.
Some encoders and streaming services have a built-in integration. You may sign in to the platform or authorise an account instead of finding and pasting a URL and key. Restream’s overview of custom RTMP destinations describes custom RTMP as the route for destinations where you need to enter endpoint details, while popular destinations may also be integrated in streaming software. The important distinction is not that one method is always better, but whether the destination and encoder support the connection you need.
When manual setup makes sense
Manual setup is useful when a platform explicitly provides an encoder URL and key, when your encoder does not offer a native preset for that destination, or when a relay service asks you to add a custom channel. It can also suit a workflow in which you control the encoder and want to send its output to a service that accepts a standard encoder feed. First make sure the destination accepts this type of connection; the word “custom” in a menu does not mean every online video service will accept any endpoint.
Where an account authorisation option is available and meets your needs, it may be simpler. You avoid copying a secret key, and some integrations can expose platform-specific controls or information that a generic destination cannot. Restream’s documentation, for example, distinguishes its native integrations from custom channels. It notes that API-dependent features such as its chat and analytics do not work on custom channels. As listed on Restream’s site in March 2026, custom RTMP channels require a paid plan. Check Restream’s current plan and feature information before relying on that route, because those terms can change.
| Connection path | What you enter | What to check |
|---|---|---|
| Built-in or account-authorised destination | Usually an account sign-in or permission grant | Whether the integration supports the controls and features you need |
| Custom RTMP destination | The destination’s server URL and stream key | That the destination accepts encoder feeds and that the endpoint is current |
| Relay service with a custom channel | The endpoint details from the final platform, entered into the relay | Plan eligibility, feature limitations and where titles or other settings are managed |
A relay adds a step: your encoder sends to the relay, which then passes the feed on to the final platform. That can be useful for a multi-destination workflow, but it also means you need to verify both the relay’s connection and the final destination. If you only need to reach one platform and its native connection works, manual setup may add complexity without solving a real problem.
For a 24/7 channel, decide who or what will keep the encoder running and recover the feed if it stops. A custom RTMP endpoint only describes where a feed goes; it does not keep your computer awake or restart a failed stream. If you are weighing a local computer workflow, this spare-PC music stream guide explains the separate operating considerations behind running a continuous YouTube channel.
Get the destination server URL and stream key
Start on the destination platform, not in the encoder. Create or select the live event, channel or destination that will receive your broadcast. Open its streaming or encoder settings and look for fields labelled server URL, stream URL, stream key, or similar. Button and tab names differ by platform, and some services show the key only after you choose a live event or reveal it deliberately.
Copy the endpoint exactly as shown. Do not construct a URL by guessing a hostname, copy one from a tutorial for another platform, or reuse an old key without checking that it is still valid for the intended stream. A destination may issue a reusable key or a session-specific one; follow its own guidance. If you are setting up a relay, be clear about which service issued each URL and key: the encoder may connect to the relay rather than directly to the final platform.
A stream key is a publishing credential. Treat it like a password: do not include it in a screenshot, tutorial video, public chat, shared document or support post. Restream’s explanation of what a stream key does offers a useful reminder that anyone with the key may be able to publish to the associated destination. If it is exposed, reset or regenerate it from the platform and update the encoder or relay with the replacement. Do not assume deleting a screenshot has revoked the key.
On YouTube, the streaming URL and key are available in Live Control Room for the live setup you are using. YouTube’s RTMPS instructions explain how to reveal the secure URL from the Stream settings when you want to use RTMPS. The ordinary RTMP URL may be displayed by default, so check which protocol you intend to use and select the matching URL. Do not paste an RTMPS URL into a field configured for a different protocol unless the encoder’s instructions say it supports that combination.
Before leaving the platform page, check whether the event is scheduled, private, unlisted or public, and whether it is ready to receive a feed. Those settings govern what viewers can see and when; they are separate from the endpoint connection itself. Keep the destination page open if it provides a preview or status indicator, so you can confirm reception after starting the encoder.
Choose Custom RTMP in your encoder
Open your encoder’s stream or broadcast settings. If the destination appears as a supported preset or account connection, consider using that path first. Follow the encoder’s sign-in and authorisation prompts, then confirm the selected channel or event. A built-in connection may be less error-prone than manual copying, but it is only appropriate if it reaches the correct destination and offers the features your workflow requires.
If there is no suitable integration, look for a service selector such as Custom, Custom RTMP, or a generic streaming service option. Labels differ across programs and versions. In OBS, for instance, the relevant controls are in the stream settings, but the precise interface can change. Choose the custom option rather than selecting a named platform whose preset might fill in a different endpoint. For a relay workflow, choose the relay or its documented custom configuration, not the final platform’s settings by default.
Do not treat video encoding settings as part of a universal custom RTMP recipe. The destination may have requirements for resolution, frame rate, bitrate, codec, keyframe interval or audio format, while the encoder’s available options vary. Read the destination’s current streaming guidance and use settings it supports. Restream’s guide to connecting OBS to Restream includes recommendations for its documented OBS workflow; those recommendations are not requirements for every platform, encoder or RTMP destination.
If your production already works for another platform, do not assume its configuration will transfer unchanged. The endpoint, protocol, accepted formats and event controls are destination-specific. If you are diagnosing a feed whose audio and picture drift apart, handle that as a production issue as well as a connection issue; this guide to fixing audio and video sync in a cloud playlist stream covers a different failure mode than an incorrect RTMP endpoint.
Enter the destination details and save
Put the server URL in the encoder’s server or URL field and the stream key in the separate key field. Check for leading or trailing spaces, line breaks or accidental omissions. Some interfaces combine the URL with an optional backup endpoint or offer a separate authentication field; fill those only if the destination specifies them. Do not put the key in the URL field simply because both items were copied from the same platform page.
If you use RTMPS, select the secure URL supplied by the destination and confirm that your encoder supports that protocol. If the encoder has a protocol or service dropdown, the selection must agree with the endpoint. A mismatch can prevent connection even when the key is correct. Keep credentials private while you work, especially if you are sharing a screen or recording a setup tutorial.
Save or apply the settings before starting the broadcast. If the software asks whether to store the key, consider who else can access that computer or account. A shared production machine may expose saved credentials to other operators, while repeatedly re-entering a key creates its own risk of copying it incorrectly. Use the access controls and key-management guidance provided by the destination.
If you are using a relay, check the relay’s channel setup separately. Restream’s documented route is to open Channels, add a new Custom RTMP channel, enter the platform-provided URL and key, and add the channel. As listed on Restream’s site in March 2026, its custom channel workflow required a paid plan, and titles for those channels had to be changed on the end platform. Confirm the current interface and plan terms before relying on those details. After saving, verify that the relay recognises the channel, then check the downstream platform after sending a test feed.
Verify the feed on the destination platform
Start the encoder when the destination is ready to receive the stream. Return to the platform’s live dashboard, preview or status area and wait for it to report an incoming feed. The exact status text and how long it takes to appear vary. The key test is whether the destination receives the right picture and sound, not merely whether the encoder says it is connected.
Check the preview before inviting viewers. Confirm that the intended scene is visible, audio is present at a sensible level, and the correct event or channel is selected. For a scheduled YouTube stream, check its Live Control Room rather than relying only on an encoder indicator. If you use a relay, confirm both the relay’s input and the final platform’s reception. A green indicator at only one point in the chain does not prove that the whole route is working.
If no feed appears, work through the chain in order. Reopen the destination’s current encoder settings and compare the URL and key character by character. Confirm the selected protocol, remove accidental spaces, and make sure the live event is the one associated with that key. If a key has been reset, update the encoder; old saved credentials will not automatically become valid. Then check the destination’s stated format requirements and encoder error messages before changing multiple settings at once.
Keep the first test controlled. If the stream is intended to run unattended, observe it long enough to verify that the file or scene repeats as expected and that the platform continues to receive it. A successful initial connection is not the same as a tested overnight operating plan. This guide to choosing a playlist or OBS loop for a 24/7 meditation stream can help you think through the content source separately from the custom destination settings.
Can I use RTMPS instead of RTMP?
Often, if the destination offers an RTMPS endpoint and your encoder supports it. RTMPS is RTMP sent over a TLS/SSL connection, adding encryption in transit. YouTube describes RTMPS as a secure extension to RTMP and provides instructions for selecting its RTMPS URL in Live Control Room. It is not safe to infer that every service uses the same endpoint or port: use the destination’s secure URL and protocol guidance.
For YouTube, reveal the RTMPS URL in the stream settings and enter that URL with the matching YouTube stream key in the encoder. Check that the encoder has an RTMPS option or a YouTube RTMPS preset. YouTube’s help guidance says to check encoder support and update it if needed. If the encoder reports an SSL error, YouTube advises checking that both the protocol and server use rtmps; it also suggests specifying port 443 if the URL appears correct but the error persists. Treat that as YouTube-specific troubleshooting, not a port rule to apply to other destinations.
Do not change only the word rtmp to rtmps in a URL unless the destination says to do so. The host, path, key and supported protocol may all be specific to the service or session. If the secure endpoint is unavailable in the destination’s instructions, ask its support team or use its documented connection method rather than guessing.
Before you make it unattended
A custom destination configures the publishing route; it does not settle the operational questions around a 24/7 channel. Decide what produces the content, what happens when the source file ends, who can access the key, and how you will notice a stopped or silent feed. Run a supervised test that covers the ordinary transitions in your programme, such as a playlist changing track or a loop returning to its beginning.
If a local encoder runs continuously, account for power, internet interruptions, software updates and computer sleep settings. A short successful test cannot show what will happen during a long outage or after an unattended restart. Make a recovery plan that fits your own equipment and platform requirements, and verify it rather than assuming a stream will resume correctly. For a cloud-based prerecorded workflow, StreamNeo removes the need to leave your own computer running to send an uploaded video continuously; the destination and YouTube setup still need to be correct.
Finally, keep a private record of which destination issued each key, which event it belongs to and where the matching settings live. Do not store the actual key in an unsecured note. If you rotate a credential, update the right encoder or relay and test again. These small checks make later troubleshooting faster without turning an endpoint copied once into a permanent assumption.
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
How to set up a custom RTMP channel
Confirm that the destination accepts encoder feeds, then create or select the live destination and copy its current server URL and stream key. Choose Custom RTMP in the encoder or relay, enter each detail in the matching field, save, start a test and verify the feed on the destination platform. Use the destination’s instructions for its protocol and encoding requirements.
How do I get my stream key?
Find it in the destination’s live-stream or encoder settings, often after selecting a specific event or channel. Copy it only from the platform or service that will receive the feed, and keep it private like a password. If it is exposed, reset it there and replace the saved key in your encoder or relay.
Can I use RTMPS instead of RTMP?
Use RTMPS when the destination provides an RTMPS endpoint and your encoder supports it. On YouTube, reveal the secure URL in Live Control Room and enter it with the corresponding stream key. Do not guess another service’s endpoint or port based on YouTube’s instructions.
Do I always need to set up a custom destination manually?
No. Some platforms have built-in account integrations or presets in popular encoders, which may be simpler and may preserve platform-specific features. Use manual URL-and-key setup when the destination or workflow calls for it, and check current plan and feature requirements if you route through a relay.