A Mac mini can send a pre-recorded video to YouTube as a live broadcast by playing a local file through OBS Studio and connecting OBS to a YouTube Live event. You still need to start the encoder, check the incoming preview in YouTube’s Live Control Room, and click Go live when the feed is ready.
That is different from uploading a video to your channel: an upload becomes a regular video, while this workflow sends the file as an encoder feed to a live event. The Mac mini must stay on and connected while OBS is broadcasting; a video file by itself does not keep a live stream running.
What this workflow does
The Mac mini runs OBS, which reads the chosen file and sends its audio and video to YouTube over the internet. YouTube receives that encoder feed and presents it within the live event you create or schedule in YouTube Studio. Viewers watch the event, not a regular video upload.
The practical sequence is: prepare the event in YouTube Studio, add the local video to an OBS scene, connect OBS with the event’s stream URL and key, start the encoder, inspect the preview, and then launch the event for viewers. For a scheduled event, the preview is the important handoff: it lets you catch a missing source, silent audio, or an incorrect file before you go live.
This guide uses OBS Studio on macOS because its Media Source can play a local file. OBS documents common media formats including MP4 and MOV, but that is not a promise that every file will work. Test the exact file in OBS, including its sound and picture, before relying on it for a scheduled broadcast. See OBS’s Media Sources guidance.
The Mac mini model and the file’s resolution, frame rate, codec, and length all matter to how smoothly a particular setup behaves. The available guidance does not establish a performance ceiling for every Mac mini, so do not treat a model name alone as proof that a chosen output setting will work. Test the actual scene and connection you intend to use.
Create or schedule the YouTube event
Open YouTube Studio and go to the Live Control Room. If this is the first time your channel has used live streaming, YouTube says that enabling it may take up to 24 hours. Do not leave the first activation until just before a planned broadcast; confirm that you can create a live event well ahead of time. YouTube’s encoder setup instructions describe creating or scheduling an encoder stream.
Set the event’s title, description, visibility, and other details in YouTube Studio. YouTube offers public, private, and unlisted visibility settings. Pick the one that matches how you intend viewers to find the broadcast, and check the event page in Studio before you send the encoder feed. The exact controls may change, so follow the current Live Control Room prompts rather than assuming an old screenshot matches your account.
Scheduling gives you a watch page and a planned start time before the encoder begins sending video. That does not mean the event has received the video file, nor does it begin the broadcast on its own. The OBS feed must arrive, and for a scheduled stream you then use the Live Control Room’s Go live control to make the event live to viewers.
YouTube advises preparing an encoder setup at least two hours before an event and starting the encoder at least 15 minutes before its scheduled start. Those are YouTube’s preparation recommendations, not guarantees that a connection or source will be problem-free. They leave room to see whether the preview arrives and to resolve issues before the planned time. Refer to YouTube’s streaming tips.
If live streaming is unavailable for your channel, resolve that before configuring OBS. For readers in India, our guide to checking YouTube Live availability in India covers that separate channel-readiness problem. Do not confuse an unavailable feature with a faulty Mac mini or an OBS connection issue.
Add the local video in OBS
Install and open OBS Studio on the Mac mini, then create a scene for this broadcast. A scene is the composition OBS sends: it can contain a Media Source for the video and, if needed, other elements such as text or a logo. For the simplest setup, use a single scene and add only the video you need. This makes it easier to see what the encoder is actually sending.
In the Sources area, add a Media Source and select the local video file. OBS’s source settings include controls for how the media is played. Check the source in the main OBS preview: the picture should be visible and correctly framed, and the audio meter should respond when the file plays. A black frame or a silent meter at this stage is easier to fix than after the YouTube event is live.
Keep the file in a location the Mac mini can access throughout the broadcast. If you use an external drive, make sure it remains connected and that the selected file is not moved or renamed. External storage is optional; the relevant point is that OBS needs access to the source for as long as it is playing. A separate local recording, if you choose to make one, also needs its own storage planning.
Check that the file itself plays from beginning to end in OBS before building the rest of the event around it. A file extension is not enough to establish that the video and audio will decode correctly on your setup. This is especially useful if the file was exported by another application or copied from a different device. OBS documents supported source behaviour and formats in its Media Sources page; use that documentation and a real playback test rather than assuming universal format support.
If the video is intended to be one segment in a playlist rather than a single repeating file, OBS documents a VLC Video source for playlists, and notes that VLC must be installed for that source to appear. That is a distinct setup from adding one Media Source. Choose it only if a playlist is actually required, and test the order and transitions before scheduling the event.
Choose whether to loop the file
Decide what should happen when the file reaches its end. In the Media Source properties, Loop controls whether playback begins again after the file completes. OBS documents this setting as off by default, so enable it deliberately when continuous replay is the intended behaviour. If the file should play once and then stop, leave Loop off and plan what you want the audience to see or hear afterwards.
For a devotional channel, for example, a file of bhajans intended to repeat overnight needs a loop; a one-time announcement or a scheduled bulletin may not. Do not infer the intended behaviour from the fact that the source has been added. Check the Loop box in the source’s properties, then let the file reach its end in a test if you need to confirm how it restarts.
A loop repeats the same source; it does not create new material, repair a gap inside the file, or keep OBS connected if the Mac mini sleeps or loses its network. If an abrupt restart would be noticeable, prepare the video so its beginning and ending make sense together. You can also choose a playlist source for multiple files, but that adds another component to verify.
For an always-on stream, the difference between a video that ends and one that repeats is an operational decision, not a YouTube setting. Include that decision in your run sheet so that someone checking the stream knows whether a stopped or repeated picture is expected. For broader planning around sustained playback, see how to keep a 4K 60fps YouTube live stream running 24/7, while keeping your own file and output settings within what your setup can reliably send.
Connect OBS with the stream URL and key
In YouTube Studio’s Live Control Room, open the stream’s encoder settings and find the stream URL and stream key. In OBS, open the streaming settings and enter the connection details provided for the event. YouTube’s live stream settings help explains these values and the role they play in connecting an encoder.
Treat the stream key as a credential. YouTube Help describes stream keys as “like your YouTube stream’s password and address”. Do not include it in a public screenshot, paste it into a public post, or send it to someone who does not need access. If it is exposed, use YouTube Studio’s controls to manage the key rather than assuming that changing the OBS scene makes the old key private again.
When entering settings, make sure you are using the URL and key for the intended event or stream setup. A feed going to the wrong event can be confusing even if OBS reports that it is connected. Keep the Live Control Room open so you can confirm that the expected event is receiving the feed. If you have previously set up a command-line encoder, the same care around credentials applies; our guide to keeping a YouTube stream key out of FFmpeg command history explains why secrets should not be left in places that are easy to expose.
Choose output settings appropriate to both the source and your upload connection. YouTube’s current general encoder guidance recommends RTMP or RTMPS, constant bitrate (CBR), a two-second keyframe interval, and compatible video and audio codecs. It recommends RTMPS for encrypted transport where supported. Follow the current YouTube live encoder settings rather than assuming every available OBS option is equally suitable.
For H.264, YouTube lists 5 Mbps as the minimum and 14 Mbps as the recommended bitrate for 1080p at 30 fps. For 720p at 30 fps, it lists 3 Mbps minimum and 8 Mbps recommended; for 1080p at 60 fps, it lists 6 Mbps minimum and 17 Mbps recommended. These are YouTube ingestion recommendations, not guarantees of picture quality or a Mac mini benchmark. Higher settings require more reliable upload capacity, and the appropriate choice depends on the codec, resolution, and frame rate. Test a setting against the actual connection before the event.
Check the Live Control Room preview
Start streaming from OBS while the event is still scheduled. This starts the encoder feed; it does not by itself perform the scheduled event’s Go live handoff. Wait for YouTube’s Live Control Room to show the incoming preview, and check it rather than relying only on OBS’s local preview. The local preview shows what OBS composes; the YouTube preview confirms that a feed has reached the destination.
Look at the picture, framing, and movement. Listen to the feed if the interface provides monitoring, and check that the audio meter in OBS behaves as expected. A picture that is present but silent, a source that is cropped, or a feed that has not arrived are reasons to pause and correct the setup before broadcasting to viewers. Do not click Go live merely because OBS says it has started sending.
Allow for the fact that the incoming preview may take time to appear. Use YouTube Studio’s status and current prompts to decide whether the feed is ready. If the preview remains absent, check that OBS is streaming, that the correct event and stream key are in use, and that the Mac mini is online. Make one change at a time, then check the result again so you know what addressed the issue.
A short rehearsal is useful even when the source is a finished file. Test the exact scene, output settings, audio, and upload connection you plan to use. If your channel relies on long, uninterrupted playback, review what can interrupt the encoder and how to respond; our article on OBS streams that will not reconnect for a 24/7 playlist is relevant to that separate continuity problem. No preview check can promise future connection stability, but it can catch a bad handoff before the event starts.
Start and monitor the scheduled broadcast
Once the preview in Live Control Room is correct, use YouTube’s Go live control for the scheduled event. This is the step that hands the ready encoder feed to the live event. Confirm the event status in Studio and, where practical, check its viewer-facing page from another device or browser. That helps distinguish a healthy control-room preview from an event that is not visible as you intended.
During the broadcast, keep an eye on OBS and the Live Control Room. Check that the source continues playing, that audio remains present, and that YouTube is still receiving the encoder feed. For a looped source, the file should return to its beginning when it ends; a test beforehand can reveal an awkward restart or a gap. If the Mac mini is dedicated to this job, prevent sleep for the planned broadcast and avoid moving or disconnecting the source file.
If the feed drops, use the status and error information shown in YouTube Studio and OBS to identify whether the problem is the encoder, network, or source. Do not assume that an event that has been launched will recover exactly as you expect. A person responsible for the channel should know how to check the connection and what to do if the source stops. For a truly unattended 24/7 operation, a desktop workflow has a practical limitation: the Mac mini, OBS, local file, power, and internet connection all remain part of the chain.
If keeping a computer running and watching for interruptions is the pain point, StreamNeo removes that particular need by letting you upload a video, provide the YouTube stream key, and have the broadcast continue with your computer switched off. It is YouTube-only; it does not change the need to prepare the file and channel correctly.
When the broadcast is finished, stop the stream deliberately in OBS and follow the Live Control Room prompts to end the event. YouTube says streams under 12 hours are automatically archived, but do not confuse that YouTube archive with a local OBS recording. If you record locally as well, verify that the local file is saved where you expect; YouTube’s encoder setup guidance and streaming tips discuss ending and archiving streams.
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
Is streaming a pre-recorded video the same as uploading it?
No. Uploading creates a regular YouTube video, while this workflow sends a file through OBS as the encoder feed for a live event. Create or schedule the event separately, connect the encoder, and check the incoming preview before using Go live.
Can I loop a video on YouTube Live with OBS?
Yes. Add the local file as an OBS Media Source and enable its Loop option if it should replay after it finishes. OBS documents Loop as off by default, so verify the setting rather than assuming the source will repeat.
Do I need to keep the Mac mini on?
Yes, for this OBS workflow the Mac mini runs the encoder and accesses the local file while the broadcast is being sent. It also needs a working internet connection. If you need the stream to continue with your computer switched off, this desktop setup does not meet that requirement.
What should I check before clicking Go live?
Make sure the intended event is receiving the OBS feed and that the Live Control Room preview shows the right picture and audio. Check the source, stream URL and key, and connection status if the preview is missing or wrong. Start the encoder early enough to resolve issues before the scheduled broadcast.