If your OBS recordings use HEVC, convert them to H.264 when you need H.264 upload files; changing a filename or container does not change the video codec. Conversion and playlist creation are separate jobs: first make and check the files, then upload them to YouTube and add them to a playlist.
You do not need to convert every OBS recording. YouTube accepts multiple upload formats, but its recommended upload settings specify MP4 with H.264 video. The practical workflow below uses HandBrake to batch transcode, keeps your originals untouched, and checks the resulting codec rather than trusting a .mp4 extension.
Conversion and playlist creation are separate jobs
A video file has a container and one or more streams inside it. The container is the wrapper—MP4 and MKV are examples—while the video stream is encoded with a codec such as HEVC (also called H.265) or H.264. Transcoding decodes the original stream and encodes a new one; it is the step that changes HEVC video into H.264 video.
Remuxing moves existing streams into a different container without re-encoding them. It can be useful when a container is inconvenient, but it does not turn HEVC into H.264. OBS explains that MKV can be remuxed to a more compatible container, while its video codec remains the same. If you need a refresher on the distinction, the OBS format guide covers containers and codecs.
A YouTube playlist is an organisation of videos on your channel. It is not created by transcoding, by naming files in sequence, or by putting them in a folder. After you have uploaded and processed the videos, create or populate a playlist in YouTube Studio and order the uploaded videos there. If the goal is a continuous broadcast rather than an ordinary collection viewers play, see the separate workflow for updating a 24/7 radio playlist without stopping the stream.
This separation helps you diagnose problems. If a local file has the wrong codec, fix the file before upload. If it plays correctly but is missing from the intended YouTube playlist, the remaining work is in channel organisation, not conversion.
Identify the source and protect the recordings
Start by confirming what OBS actually recorded. OBS recording settings can use different containers and encoders, and a file extension alone does not tell you which codec is inside. Open a sample in a media-information tool or a player that reports stream details. Look for the video codec, resolution, frame rate, audio streams, and whether the source is HDR or 10-bit.
If the video stream says HEVC or H.265, and you need H.264 upload files, plan to transcode. If it already says H.264, conversion may be unnecessary. YouTube's upload recommendation is not a rule that every OBS recording must be re-encoded; weigh compatibility against the time and quality cost. For example, if your source is already H.264 in a suitable MP4 and plays as expected, another lossy encode can reduce quality without solving a problem.
Keep an untouched copy of every original. Create a separate output folder, such as youtube-h264, and leave the source recordings where they are. Give each output a distinct, recognisable filename that retains episode names or ordering—01-morning-bhajan-h264.mp4 is easier to identify than output-1.mp4. Never use the same destination name for different sources: a queue job that overwrites an earlier result can silently remove a file you meant to keep.
Preserving originals matters because transcoding is lossy, even when the result looks close to the source. HEVC is generally more efficient than H.264, so an H.264 output may be larger at comparable visual quality. If you later discover a wrong crop, missing language track, or colour shift, you can return to the original rather than transcoding an already degraded copy.
Choose a HandBrake Creator preset
HandBrake is a graphical option for this workflow, and its official Creator presets are intended for video-hosting uploads. The current documentation lists Creator presets for 720p60, 1080p60, 1440p60, and 2160p60. Those names indicate a resolution and frame-rate class, not a promise that every source should be enlarged or converted to 60 frames per second.
Choose the Creator preset that best matches the recording you have and the output you need. For a 1080p recording at 30 frames per second, do not pick a 1080p60 preset simply because its number looks higher. Preserve source dimensions and frame rate unless you have a clear editing reason to change them. YouTube advises encoding and uploading at the same frame rate as the recording.
After selecting a preset, inspect its settings rather than treating the preset name as proof. HandBrake may expose settings for cropping, scaling, filters, video encoder, audio, and subtitles. Check that automatic cropping has not removed content near the edge, scaling has not changed the intended resolution, and filters are not introducing an unwanted change. A preset is a starting point; the source and the intended output remain your responsibility.
Creator presets use MP4, H.264, and AAC stereo according to HandBrake's documentation. That is a straightforward combination for a standard upload, but a source can contain multiple audio languages, commentary, or unusual channel layouts. Check the audio and subtitle tabs for each source type before committing to a batch. The setting that worked for one recording might not select the right track in another.
Set and verify H.264 in an MP4 container
In HandBrake's Video settings, explicitly confirm that the video encoder is H.264 (x264 or an available H.264 hardware encoder), rather than H.265/HEVC. In the Summary or output settings, confirm that the container is MP4. These are separate checks: an MP4 file can contain HEVC video, and an H.264 stream can be placed in a different container.
When the interface offers “Same as source” or an equivalent frame-rate choice, preserve the source rate unless your edit requires a change. Confirm the displayed dimensions against the source. Be cautious with automatic anamorphic, crop, and scaling settings if the image edges, aspect ratio, or black bars matter. A small test encode lets you spot an unexpected crop before you repeat it across a full collection.
Consider whether the software encoder or hardware encoder suits the job. Software H.264 encoding can take longer and use more processor time; supported hardware encoding can shift some of that work to the graphics or media hardware, but availability and output characteristics vary by device and driver. OBS's hardware-encoding guidance is useful context, though it discusses encoding support rather than prescribing a universal HandBrake setting. If your computer is already busy or the files are long, test one representative file and compare the result and processing time before selecting an approach for the batch.
Audio needs its own check. The Creator preset's AAC stereo output is a broadly compatible choice for an MP4 upload. YouTube lists AAC-LC, Opus, or Eclipsa Audio among audio codecs in its recommended settings. HandBrake can re-encode audio or pass through supported formats; passthrough retains the selected audio stream as-is, but it does not guarantee that every source format or track arrangement is suitable for the intended output. Confirm the language and track you want, and listen to the result.
Treat HDR and 10-bit footage as a separate case. Do not blindly run it through an SDR-oriented conversion and assume colour will remain correct. YouTube's live-stream documentation discusses H.265 in an HDR live-encoding context, which is not the same as a recipe for prerecorded uploads. If preserving HDR matters, check current guidance for your editing and upload path, and test with a short sample before converting the archive.
Batch-convert files with the queue
Once a test output looks right, prepare the batch. Keep source files in their own folder and send all outputs to the separate destination folder. Decide on a naming pattern that preserves playlist order and episode identity. Before queueing, confirm that every job points to a unique output filename; automatic names are convenient only if you have checked how HandBrake derives them for your sources.
HandBrake's queue documentation describes adding jobs and processing them when ready. In the graphical app, open a source, choose its preset and destination, then add that job to the queue. Repeat for each file, checking the source and destination before adding it. Depending on the app version and platform, you may be able to open a folder or add multiple sources; verify what the interface has actually loaded rather than assuming a folder selection has queued every file.
When the list is complete, review the queue for duplicates, missing items, and name collisions. Check the preset and output destination on a few jobs, especially if the source recordings differ in frame rate, resolution, audio tracks, or colour properties. Then start the queue and let it finish. If the computer sleeps or the application closes during processing, a job may not complete, so check the queue status and output folder before moving on.
For a recurring workflow, HandBrakeCLI can make repeatable batch conversion practical, but command options depend on the installed version, source tracks, and output paths. Do not copy an untested command from a different machine and run it across the archive. Verify the installed CLI's encoder and options, test one input, inspect the result and log, and use a script that gives each source a unique destination. Stream-copying the video is not a shortcut for this purpose: it would preserve the HEVC stream rather than create H.264.
A well-organised batch is easier to recover if one file fails. Keep a simple record of source filename, output filename, and whether the output passed inspection. If one job has no output or an incomplete file, re-run that job rather than guessing whether the rest of the queue succeeded. For long-running channels with changing video collections, a documented order also reduces duplicate or missing episodes; the guide to preventing duplicate episodes in a 24/7 story playlist covers that organisation problem separately.
Check the converted files before uploading
Do not treat a completed progress bar or .mp4 suffix as verification. Inspect the actual output streams with a media-information tool. Confirm the video codec says H.264/AVC, the container is MP4, the duration is plausible, and the resolution and frame rate match the plan. This directly checks the outcome you wanted: a newly encoded H.264 video stream, not a renamed HEVC file.
Play the start, middle, and end of a representative output. Look for a black frame, unexpected crop, stretched aspect ratio, colour shift, stutter, or audio that drifts out of sync. Listen for the intended language or programme audio and check that sound is present throughout. If subtitles were part of the source, confirm whether they were retained, burned into the picture, or intentionally omitted. A file can be technically H.264 and still be wrong for the channel.
If the batch includes materially different source types, inspect a sample from each type rather than relying on one test. For example, a standard SDR recording and an HDR source should not be treated as interchangeable. A good check before upload is less costly than discovering a colour or track problem after uploading a whole playlist's worth of files.
Keep the originals even after the checks pass, at least until you have confirmed YouTube has processed the uploads and the published videos play as expected. If the converted files are much larger than expected, review the source efficiency and quality settings rather than deleting the originals to reclaim space immediately. Do not chase an arbitrary file size: visual quality, upload time, available storage, and reliable playback all matter.
Upload the files and build the playlist
Upload the checked files through YouTube's normal upload flow. Give each video a clear title and description, and keep the title/order scheme aligned with the local filenames so that you can identify each item later. Wait for processing and check playback before adding a video to a public playlist. YouTube may offer processing choices and timing that can change; check the current Studio interface rather than relying on a menu path that may have moved.
Once videos exist on the channel, create a playlist or add the uploads to the intended existing one in YouTube Studio. Arrange the order there and confirm the playlist's visibility setting matches your plan. Uploading several files does not by itself make them a playlist, and their local filename prefixes do not determine how viewers see them. If you're planning a long-running music or devotional channel, file preparation is only one part of maintaining the live schedule; see how to replace a video in a running 24/7 Indian music stream.
A YouTube playlist of uploaded videos is also distinct from a prerecorded live stream that loops video content continuously. For that use, decide how the broadcast will keep running after your computer is switched off and how you will replace files without disrupting viewers. StreamNeo removes the need to keep a local computer running for a file-based 24/7 YouTube broadcast: you upload a video and use your YouTube stream key, while the playlist-upload workflow above remains a separate channel task.
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
Does changing .mkv to .mp4 convert HEVC to H.264?
No. Renaming a file changes only its name, and remuxing changes the container while keeping the encoded streams. To change HEVC video into H.264, use a transcoder to decode and re-encode the video stream.
Do I need to convert every OBS recording for YouTube?
No. First check the codec and whether the file suits your upload and playback needs. If the recording is already H.264 in a suitable format, another lossy encode may add time and reduce quality without helping; if it is HEVC and you want H.264, transcode it and verify the result.
Can HandBrake make a YouTube playlist for me?
No. HandBrake converts local files; it does not create a playlist on your YouTube channel. Upload and process the videos, then create or populate the playlist in YouTube Studio.
Should I convert HDR or 10-bit OBS recordings with the same settings?
Not without checking the colour workflow. An SDR-oriented conversion can alter the appearance of HDR material, and there is no universal HDR-to-H.264 recipe here. Preserve the original, check current guidance for your intended upload, and test a sample first.