When an FFmpeg YouTube Live promo playlist stops at a filename containing spaces, first check whether the concat demuxer is reading a text playlist and how that playlist spells the path. Quoting the playlist filename in your shell protects it from shell parsing; it does not quote the media filenames written inside the playlist.
That makes playlist syntax a sensible first check, not a confirmed diagnosis. Without the command, the relevant playlist line and the error output, a missing file, an invalid path, an incompatible clip or a later publishing failure could look similar.
First establish what FFmpeg is reading
A concat-demuxer input is a text script that lists the media files to process, usually one file directive per entry. You may see a command shaped like -f concat -i list.txt, or a list beginning with ffconcat version 1.0. Those clues point to the concat demuxer, whose list has its own syntax. FFmpeg documents that format in its formats documentation.
Do not assume every file called a playlist is a concat list. An M3U8 file, a wrapper that generates a command, and a shell sequence can all play a part in a live workflow, but their parsing rules are not interchangeable. If you are unsure, look at the command and the first few lines of the input file before editing anything.
The failure stage matters. Does FFmpeg reject the list as it opens the input, complain that it cannot open one of the listed files, or read the clips and fail only when publishing the output? Note the first meaningful error and the lines immediately before it. A later error can be the consequence of an earlier one, while a live-output error may have nothing to do with the local filename.
If the command is managed by a script or application, inspect the actual list it produced rather than only the template or settings that were meant to create it. A generator can put paths on the wrong lines, leave out a directory, or write quoting intended for the shell into a file parsed by FFmpeg.
Shell quoting and playlist quoting are separate
A shell reads the command line before FFmpeg does. Quotes around list.txt can prevent the shell from splitting that input path at a space. Once FFmpeg opens the list, the concat demuxer reads its contents according to concat-script rules. It does not inherit the shell’s interpretation of those contents.
For example, shell quoting the list input cannot repair a line inside it that leaves a media path with spaces unquoted. Conversely, editing a path in the list does not fix a shell that splits the list filename itself. Diagnose these as two separate boundaries: first, can the process open the list file; second, can the concat demuxer interpret each entry and open the media file it names?
This distinction is useful when a setup works for ordinary names but fails after someone renames a clip to something descriptive, such as summer sale intro.mp4. The rename may expose a path-parsing issue, but it may also have changed the directory or spelling. Compare the exact path before and after the rename rather than inferring the cause from the presence of spaces alone.
If you share a command for help, redact the YouTube stream key and any other credentials. Keep the input and output structure visible, and include the relevant playlist line. The key is not needed to diagnose how FFmpeg reads a local concat list.
Quote a path with spaces in the concat list
The FFmpeg concat documentation says that special characters and spaces in a file path must be escaped with a backslash or enclosed in single quotes. Its example for a path with spaces uses this form:
file '/mnt/share/file 2.wav'
Apply that pattern to the entry in the concat list, replacing the example path with the real path to your own file. Do not paste the example as a corrected command for an unknown directory, operating system or filename. The significant point is where the quoting goes: around the path following file in the list, not merely around the list’s name after -i in a command.
After changing the line, check that the quotes are balanced and that they surround the entire intended path. A path with spaces in more than one component still needs to be represented as one path. If a tool generates the list, inspect its output: it must emit valid concat syntax for the actual filenames, not simply put shell quotes around every value.
Keep the first test small. If the list contains many clips, make a copy and test the failing entry in a short list with the same relevant path and options. That can help establish whether list parsing is involved without changing the production playlist. Preserve the original and avoid making several unrelated edits at once; otherwise a successful run will not tell you which change mattered.
The documentation on the FFmpeg site is regenerated and reflects the newest revision, so compare it with the installed build rather than assuming every older binary behaves identically. You can record the output of ffmpeg -version for support or for your own notes. The installed version is part of the evidence, especially if a command copied from a newer guide behaves differently.
Handle quotes and other special characters carefully
A space is not the only character that can make a list entry ambiguous. A filename may itself contain a single quote, a backslash, or other punctuation. In that case, do not guess that shell escaping will carry into the concat file. Follow the concat demuxer’s documented escape form for the exact character, and keep the result within the list-file syntax.
For a filename containing a single quote, the FFmpeg documentation shows an escaped form rather than treating a shell-quoted command as a universal solution. This is a point where copying a generic example can do harm: escaping rules vary by layer. The shell, a program that writes the list, and the concat parser may each process characters at a different time.
If the names are generated, a robust approach is to use a list-writing method that understands concat syntax, or to rename troublesome files to simple names and update the entries consistently. Renaming is not a universal requirement and may not suit an archive or a workflow with references elsewhere. It is a practical simplification when you control the files and can verify that every playlist path was updated.
Avoid broad search-and-replace across a list until you understand which layer added the characters. A backslash that is appropriate for one parser may be interpreted by an earlier parser, removed, or passed through literally. Make a backup, change one representative entry, then run a focused test and inspect the output before applying the same transformation to the rest.
Check safe-path rules, working directory and access
The concat demuxer’s safe option defaults to 1. FFmpeg defines safe paths as relative, without a protocol specification, and made from letters, digits, a period, an underscore or a hyphen; a path component must not begin with a period. A space is outside that documented character set, so a correctly quoted entry can still meet a separate safe-path restriction.
The option -safe 0 relaxes that validation and accepts any filename. Consider it only when the list and the paths it names are trusted and locally controlled. It is not a repair for a typo, a missing file or a path the FFmpeg process cannot read. Do not use it to make an untrusted list acceptable; relaxing validation does not make arbitrary inputs safe.
Relative paths depend on the process’s working directory. The directory may differ when you launch FFmpeg by hand, run it from a scheduled task, start it through a service, or call it from a wrapper. Confirm the working directory in the actual execution context and check that each listed file exists there or is addressed by a suitable path. Also check permissions and whether a mounted or removable drive is available to the process.
Be consistent about path style for the operating system and environment in which FFmpeg runs. A path copied from a different machine may look plausible while pointing nowhere in the current environment. Do not replace it with an invented absolute path; inspect the real directory structure, then test the exact entry from the same context that runs the stream.
A file-open error after the list has been parsed is different from a parse error. Record whether FFmpeg identifies a particular path, says it cannot open a file, or rejects the concat input itself. That wording narrows the next check, but retain the full surrounding log: a shortened message can hide whether the failure arose from a missing file, permissions, malformed syntax or another input issue.
Confirm the clips can be concatenated
Getting past a path error does not guarantee that the sequence can be joined as intended. FFmpeg’s concat demuxer expects the inputs to have matching streams, codecs and time bases. Promo clips exported from different editing presets may differ in those properties even when each plays correctly on its own.
If the playlist opens but FFmpeg reports stream or timing problems as it moves between clips, compare the media properties rather than continuing to change filename quoting. A path correction can expose a second, independent problem. For a sequence that needs conversion into a common format, FFmpeg’s FAQ on concatenation describes the concat filter as an option when re-encoding is needed.
| Method | Consider it when | Main trade-off |
|---|---|---|
| Concat demuxer | You want to join compatible inputs without re-encoding. | The list needs valid concat-script paths, and the input streams must meet the demuxer’s compatibility requirements. |
| Concat filter | Clips need to be brought into a common format or re-encoded. | You need an encoding and filter workflow, not just a list that stream-copies files. |
| Concat protocol | Your container supports file-level concatenation. | FFmpeg describes this as limited to selected container formats, so it is not a general replacement for a playlist. |
Choose by the files you have and the output you need, not by which method uses the shortest command. If you need to preserve the clips without re-encoding, first establish that their streams are compatible. If they are not, plan a conversion workflow and check the resulting sequence before using it for a continuous broadcast.
For a YouTube channel that is meant to carry a repeating sequence, a reliable local test is worth doing before you depend on it overnight. The considerations in keeping a live stream active when a video ends are relevant once playback and transitions work, but they do not replace diagnosing an input-list failure.
Separate local input trouble from live-output trouble
If FFmpeg opens the list and progresses through the clips, look later in the log for the first output-side error. Identify the protocol and destination type actually in use. A local RTMP publishing failure, an authentication issue and an HLS ingestion response are not evidence that a filename was parsed incorrectly.
YouTube’s HLS ingestion documentation describes server responses including HTTP 400 for a malformed URL or an unparseable or unsupported playlist, and HTTP 401 for a corrupted or expired cid parameter. Those are meanings for responses at the YouTube HLS interface, not a diagnosis of a local concat-list line. First establish which side emitted the error and whether FFmpeg had already read the media inputs.
Likewise, do not treat a YouTube stream key or ingest destination as a remedy for a local file-open error. Keep credentials private while collecting logs, and distinguish the command’s input options from its output options. If you are comparing publishing methods, the practical distinctions in this guide to testing RTMP, HLS, RTSP and DASH streams can help you identify what protocol a test is actually using.
A failure that appears only after a long run may also be different from a failure at the first space-containing filename. Note whether the stream starts, how far through the sequence it gets, and whether the same clip fails in a short local test. That timeline helps separate repeat or end-of-file behaviour from a path that FFmpeg cannot open at all. For continuous playlists built from files, this overview of streaming prerecorded MP4 files to YouTube offers wider workflow context, not a substitute for the exact error.
Re-run with evidence, not assumptions
Once you have verified the list format and the real path, rerun with one controlled change. Keep a copy of the original list, note the command and working directory, and capture the complete FFmpeg output from input opening through the point of failure. The first error is often more useful than the final shutdown message.
For a useful diagnosis, retain the full command with secrets redacted, the precise failing file line, the file and directory names, the operating system and shell, the FFmpeg version, the complete error excerpt, and whether the output is RTMP or YouTube HLS. Do not include a stream key in a forum post, screenshot or support ticket. If the list is generated, include the generated line as well as the code or settings that produced it.
If the change clears a list-parsing or file-open error but another message appears, treat that as progress in diagnosis, not proof that the entire live setup is sound. Re-check stream compatibility, output settings and the destination separately. This is the same discipline used when investigating frame drops after an OBS update: isolate the stage that fails instead of changing unrelated settings all at once.
For a channel that must continue while your own computer is off, manually maintaining a local FFmpeg process can itself become a recurring operational burden. StreamNeo turns an uploaded video into a YouTube live stream, so it can remove the need to keep that local playlist process running for a file-based broadcast; it does not diagnose an unknown FFmpeg error or change the rules for content you have rights to use.
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 quoting list.txt in the command fix spaces in a clip name?
No. Shell quotes around the input protect the playlist filename while the shell parses the command. The concat demuxer separately parses the paths written inside that playlist, so quote or escape the media path there according to FFmpeg’s concat syntax.
Should I always add -safe 0 when a filename has a space?
No. The option relaxes the concat demuxer’s safe-path validation, but it cannot correct a misspelled path or make a missing file readable. Use it only for a trusted, locally controlled list, and verify the path and the exact error first.
How can I tell whether this is a local playlist error or a YouTube error?
Look at the earliest relevant FFmpeg log message and whether the listed files opened and playback advanced before the failure. A response from the output destination occurs at a different stage than a local list parse or file-open error; identify whether the workflow uses RTMP or HLS before interpreting the message.
What information should I send when asking for help?
Share the command with secrets removed, the exact list line, the FFmpeg version, operating system and shell, the full error excerpt, and the output protocol. Include enough path context to show where the file is meant to be, but never post your YouTube stream key.