For XSplit Broadcaster RTMP settings, use either its YouTube output or a Custom RTMP output, then match the encoder settings to YouTube’s current table for your chosen resolution, frame rate and codec. A VPS listing does not prove that the machine can keep sending that stream continuously; check the actual Windows and encoding environment and measure sustained outbound capacity before relying on it.
For a 24/7 YouTube stream, the safer sequence is to confirm channel eligibility, copy an RTMPS address and private stream key from Live Control Room, configure XSplit, and run a representative test. Treat the stream key as a password, and plan recording and recovery separately from the live broadcast.
Choose YouTube output or Custom RTMP
XSplit’s dedicated YouTube output is the simpler starting point if it is available in your version and the account authorisation flow works for your channel. It avoids manually typing the destination address and key, which reduces one common source of configuration mistakes. Follow the on-screen authorisation flow and make sure you are choosing the channel that should host the stream.
Custom RTMP is useful when you need to enter YouTube’s destination details yourself or want explicit control over the connection fields. XSplit’s setup guide describes entering an RTMP URL and a stream name before configuring encoding. In this case, the “Stream Name” field is where the YouTube stream key goes; keep the two fields distinct and do not paste the key into a public note or chat while setting up.
| Choice | Credential setup | What to check |
|---|---|---|
| YouTube output | Authorise the YouTube account through XSplit | Correct channel, selected stream, and available protocol and encoder controls |
| Custom RTMP | Enter the destination URL and stream key manually | Correct RTMPS URL, key in the Stream Name field, and matching encoder settings |
Both paths still need settings compatible with the active YouTube stream. A preset can be a useful starting point, but do not assume it reflects the current encoder table or the capacity of a VPS. Confirm output resolution, frame rate, codec, rate control, bitrate and keyframe interval in XSplit after choosing the output.
XSplit’s published product requirements are desktop software requirements, not a certification for every hosted machine. Its product page lists Windows 10 64-bit, 8 GB RAM and a graphics card with DirectX 10.1 or better among its minimum requirements, while also distinguishing a recommended processor from the minimum. Those requirements may change, so check the XSplit Broadcaster product page and your installed version rather than treating a generic VPS label as proof of compatibility. A virtual machine may not expose the graphics or encoding capabilities XSplit expects.
A VPS can also have operational limits beyond video encoding. Check that its operating system is supported, that a persistent desktop workload is permitted by the host, and that you can keep the machine signed in and recover it after a restart. The research available for this guide does not validate a particular provider, virtualisation platform, GPU allocation or Windows image. If your requirement is simply to send a prepared continuous file, compare the maintenance burden of a desktop encoder with a workflow that removes the need to keep your own computer on; the cloud streaming options guide explains the broader trade-offs.
Copy the current RTMPS URL and stream key
Open YouTube Studio’s Live Control Room and create or open the stream you intend to use. Copy the stream URL and stream key shown for that stream. YouTube recommends RTMPS, which carries RTMP over an encrypted TLS/SSL connection; use the current RTMPS address shown by YouTube rather than relying on an old saved address or a URL copied from an unrelated guide. See YouTube’s RTMPS encryption guidance.
For XSplit’s YouTube output, sign in through the authorised flow and select the intended channel and stream. For Custom RTMP, paste the RTMPS URL into the URL or server field and the stream key into the Stream Name field. Interface labels differ across versions, so check the field labels before saving. Do not put both values in one field, and do not assume that a stream key is interchangeable with the URL.
Before you press Go Live, confirm the stream title, visibility and intended audience in Live Control Room. If you are testing, choose a private or unlisted test where appropriate and verify that the audience setting is what you intend. Channel eligibility is separate from encoder configuration: YouTube says a channel must be verified and must not have live-streaming restrictions in the past 90 days. Check YouTube’s live-streaming eligibility help if the stream cannot be created or started.
The key point is to copy credentials for the stream you are actually opening. A key from a different event, an old saved output, or a different channel can result in a connection that does not behave as expected. If you keep more than one output in XSplit, label them by channel and purpose without including the key in the label. This makes it easier to identify the right destination without turning the interface into a credential store.
Protect and reset a compromised key
Treat the stream key like a password that can authorise a broadcast to your channel. Do not include it in screenshots, support tickets, public configuration examples, livestream overlays, shared documents or messages to someone who does not need access. Avoid saving it in a plain-text file on a shared VPS account. If another person must configure the stream, use an access-controlled account or handle the setup together without sending the key through a public channel.
A key is not safer merely because it is difficult to remember. Its job is to let the encoder authenticate to the destination, so anyone who obtains it may be able to send a broadcast using that stream configuration. Keep access to the VPS itself restricted, use a separate account for routine operation where feasible, and avoid pasting the key into shell history or command-line arguments. If the XSplit interface offers credential storage, consider who can access the Windows account and the machine’s saved profile.
If you suspect exposure, open YouTube Studio’s Live Control Room and reset or regenerate the stream key there. Then update XSplit with the new value and test again before scheduling the channel. Do not assume deleting a screenshot or changing the stream title invalidates a disclosed key. YouTube’s encoder setup help describes the stream key as the credential used by the encoder; use the current controls in Studio to manage it.
Keep a simple recovery note that records the channel, output name, last test time and where to find the Live Control Room, but not the key itself. If the machine is administered by a VPS provider or another operator, clarify who can access the Windows session and saved credentials. This is ordinary access control, not a guarantee that a broadcast cannot be interrupted.
Choose encoder settings from YouTube’s current table
Do not start from a universal bitrate. In XSplit, choose a resolution, frame rate and codec that fit the source and viewing use, then consult YouTube’s live encoder table for the corresponding recommendation. YouTube’s table specifies RTMP/RTMPS, constant bit rate (CBR), and a recommended keyframe interval of two seconds, with four seconds as the maximum. It includes different bitrate guidance for H.264, AV1 and H.265, so a figure for one codec should not be copied into another codec’s settings.
For context, YouTube’s current H.264 recommendations include 6 Mbps for 720p at 30 fps, 8 Mbps for 720p at 60 fps, 10 Mbps for 1080p at 30 fps and 17 Mbps for 1080p at 60 fps. These are YouTube’s published encoder recommendations, not a promise that your VPS can deliver them, or that every source needs the highest resolution. Check YouTube’s live encoder settings table at the time you configure the stream because the table and supported options can change.
In XSplit, set the output resolution and frame rate deliberately. A static devotional image, an ambience scene or a news loop may not need the same motion handling as a fast-moving video, but the encoder still has to send a consistent stream at the chosen format. Set rate control to CBR where available, match the selected codec to the table, and set the keyframe interval to two seconds unless the current YouTube instructions direct otherwise. Do not choose an interval beyond four seconds.
Make sure the source itself is ready at the selected dimensions and frame rate. Scaling a small source up does not create new detail, and selecting a higher frame rate does not repair judder in a low-frame-rate file. If audio and picture timing are wrong in the file, a correct RTMPS connection will not fix the underlying issue; use the audio and video sync troubleshooting guide to check the source and playback chain.
The table is a starting point, not a reason to use a setting that the machine cannot sustain. If XSplit offers separate output and preview quality controls, distinguish them: the live output must match the intended encoder specification, while local preview quality affects the machine’s workload. Recheck the actual XSplit output summary after saving a preset, because a preset name alone does not prove that each field has the intended value.
Check sustained VPS upload capacity
A VPS product page may advertise a port speed, network interface or transfer allowance, but none alone proves that the machine can sustain a particular live encoder output around the clock. Available outbound capacity can vary with the host’s network conditions, routing, the virtual machine’s allocation and other workloads. A speed test taken once is a snapshot, not evidence of a stable overnight feed.
Use YouTube’s bandwidth guidance as a planning method. YouTube advises allowing for the primary bitrate, backup bitrate and 20% headroom when estimating required upload bandwidth. If you are sending only one feed, do not silently count a backup stream as though it were absent from the guidance; determine whether your workflow uses one, and account for it if it does. The YouTube network tips explain the headroom recommendation and warn that network disruption can break a stream.
Measure outbound performance from the actual VPS and during periods that represent its ordinary use. Run a sustained transfer or repeated bandwidth checks long enough to expose drops, not just a quick test at provisioning. Observe whether the result varies at busy times, and compare the stable capacity with the full output bitrate and the headroom you planned. Avoid claiming that a given port speed, test result or provider plan establishes 24/7 suitability.
A VPS choice also depends on its Windows and encoding environment. Confirm that the selected plan actually supplies a supported Windows version and that any promised GPU or hardware encoding capability is available to your virtual machine, not merely listed as a host feature. XSplit’s desktop requirements do not establish support for a headless/server mode or every hypervisor. The reviewed material does not establish a tested VPS size or named provider for this job.
If your channel depends on continuous availability, ask the provider what happens during maintenance, account restarts, network incidents and resource contention. Check whether you can receive alerts and regain the Windows session without being physically present. Set realistic expectations: a stream may still drop because of a network interruption, an encoder failure or a YouTube-side issue. A separate local or cloud recording can protect the programme material, but it does not keep the live connection on air.
Test the stream before relying on it
Run a private or unlisted test before announcing a continuous schedule. Use the same VPS, XSplit output, source file, resolution, codec, frame rate and audio arrangement that you expect to use in production. A test from your home PC does not establish that the VPS’s upload path or virtualised encoder will behave the same way.
Watch Live Control Room’s stream health while XSplit is sending. Check for warnings, dropped frames, connection instability, audio clipping, silence, unexpected black frames and a mismatch between the chosen settings and the incoming feed. Then view the stream on a separate device or browser, rather than relying only on XSplit’s preview. For a playlist or video loop, listen through a representative transition; a brief silent gap may be tolerable for some formats and disruptive for others. The guide to preventing silence between podcast episodes covers one source-side issue that an encoder setting cannot fix.
Test recovery as well as the initial connection. Observe what happens if XSplit is closed and reopened, if the VPS restarts, or if the network path is briefly interrupted. Do this during a test window, not during a broadcast that viewers rely on. Confirm whether the output reconnects, whether the correct stream is selected after restart, and whether the machine requires an interactive sign-in. The reviewed official material does not promise automatic recovery for a particular XSplit and VPS combination, so verify your actual workflow.
Plan archives separately. YouTube’s encoder help says streams under 12 hours are automatically archived; that is not a promise that a single stream lasting 24 hours or longer will be archived in full. If you need a complete recording for later viewing, maintain a local or separate recording workflow and test the resulting files and handoff. See YouTube’s encoder stream creation guidance for the current archive guidance, and do not make an uninterrupted session’s archive your only copy.
For a recurring channel, record the tested configuration without storing the key in the same note. Include the output choice, codec, resolution, frame rate, bitrate target, keyframe interval, source file, VPS operating system and the result of the sustained test. Note what you checked after a restart. This gives you a baseline when a later change to the file, XSplit version, VPS image or YouTube settings introduces a problem.
When keeping a computer or VPS continuously available is the specific burden you are trying to remove, StreamNeo can run an uploaded video as a YouTube live stream without leaving your own computer switched on.
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
Can XSplit Broadcaster send a YouTube 24/7 stream from a VPS?
It can be configured for YouTube output or Custom RTMP, but that does not establish that a particular VPS can run XSplit continuously. Check the supported Windows and encoding environment, confirm that persistent use is permitted, and test the actual machine’s sustained upload and recovery behaviour before relying on it.
What do I put in XSplit’s Custom RTMP fields?
Copy the current RTMPS URL and stream key from YouTube Live Control Room. Put the URL in the server or URL field and the key in XSplit’s Stream Name field, then confirm the output settings against YouTube’s current encoder table.
What bitrate should I use for a YouTube stream?
There is no single bitrate suitable for every stream. Choose the resolution, frame rate and codec first, then use YouTube’s current table for that combination and check that the VPS can sustain the output with appropriate network headroom.
Will YouTube archive one continuous 24-hour stream?
YouTube says streams under 12 hours are automatically archived, which does not establish that a single 24-hour-or-longer session will be archived in full. If you need a complete on-demand recording, test a separate recording workflow rather than relying on the live archive alone.