You can use FFmpeg’s Intel Quick Sync Video (QSV) encoder to loop a local video file and publish it to YouTube, provided your computer’s Intel graphics, driver, FFmpeg build and QSV runtime support the encoder. FFmpeg’s -stream_loop -1 repeats the input indefinitely; it does not, by itself, keep the computer, network connection or YouTube ingest online indefinitely. The procedure below covers the DIY setup and the separate recovery work needed for continuous operation.
What Quick Sync does—and what you need
Intel Quick Sync is hardware-assisted video encoding and decoding available through supported Intel graphics. FFmpeg exposes QSV encoders such as h264_qsv. A compatible processor name alone is not enough to establish support: the graphics path must be enabled, and the operating system, driver, FFmpeg build and runtime must work together. Intel identifies oneVPL as the forward path for newer Intel GPU media features; FFmpeg must be built with the relevant support, and runtime implementation selection depends on the hardware and software stack. See Intel’s oneVPL and FFmpeg overview.
As an Amazon Associate I earn from qualifying purchases.
Before you begin
- A video file that you have the rights to stream, with audio if needed.
- A computer with a supported Intel graphics path and processor graphics enabled.
- An FFmpeg build whose encoder list includes
h264_qsv, plus a compatible QSV runtime and driver. - A stable upload connection with headroom above the chosen video bitrate.
- A YouTube channel that is eligible to create a live stream, and a stream key from YouTube Studio.
Confirm that Quick Sync is available
In a terminal or command prompt, run ffmpeg -hide_banner -encoders and look for h264_qsv. Then inspect that encoder’s available options with ffmpeg -hide_banner -h encoder=h264_qsv. These checks establish what the local FFmpeg build exposes; they do not prove that the runtime and driver can successfully initialize the hardware. If initialization fails, check that processor graphics are enabled in firmware and visible to the operating system. On a system with a separate, non-Intel graphics card, disabling the integrated Intel graphics can also disable Quick Sync. Intel’s support note on this point was last reviewed on 2024-09-04: Intel processor graphics and Quick Sync availability.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →On Linux, the relevant pieces can include Intel’s media driver, libva, Media SDK and oneVPL, alongside FFmpeg. Package and driver versions change; see Intel’s Graphics Media Stack overview and verify the packages for your distribution and hardware. Do not assume that all Intel processors, mini PCs or generations support the same codecs or stream modes.
Choose YouTube-compatible stream settings
YouTube’s live encoder guidance lists RTMP/RTMPS ingest and H.264, H.265/HEVC and AV1 video options, with frame rates up to 60 fps. For a broadly compatible starting point, H.264 is a practical choice because YouTube publishes H.264 recommendations and FFmpeg offers h264_qsv; that is not a claim that it produces better quality than other codecs on every machine. Use only a codec and settings supported by your actual QSV hardware and FFmpeg build.
#1 Best Overall
- Next‑Gen Platform Support: Compatible with Intel 800 Series Chipset‑based motherboards with LGA1851 Socket enabling PCIe 5.0/4.0 and high‑speed DDR5 memory (up to 7200 MT/s).
- High‑Performance Core Configuration: Features up to 24 cores (8 P‑cores + 16 E‑cores) for demanding gaming and creator
- Ultra‑Fast Boost Clocks: Reaches up to 5.5 GHz max turbo frequency for top‑tier responsiveness and performance
- Built for Enthusiasts: Unlocked for performance tuning when paired with Intel Z‑series chipsets, making it ideal for overclockers and power users.
- Robust Power & Thermal Design: Engineered with 125W base power and 250W max turbo power to sustain high‑intensity
Resolution, frame rate and bitrate
Choose an output resolution and frame rate that your source, encoder and upload connection can sustain. YouTube’s current H.264 table gives these ingest figures (accessed in 2026); they are YouTube recommendations, not guaranteed results for a particular encoder, network or video:
| H.264 output | YouTube minimum | YouTube recommended |
|---|---|---|
| 720p30 | 3 Mbps | 8 Mbps |
| 1080p30 | 5 Mbps | 14 Mbps |
| 1080p60 | 6 Mbps | 17 Mbps |
| 2160p60 (4K) | 14 Mbps | 50 Mbps |
Leave additional upload capacity for network variation rather than setting the stream bitrate equal to the connection’s best-case speed. YouTube advises testing with similar motion and audio before relying on a stream, then monitoring stream health. A static image may encode differently from fast-moving footage, so test a representative section of the actual file.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #2
- Game Without Compromise. Play harder and work smarter with Intel Core 14th Gen processors
- 20 cores (8 P-cores plus 12 E-cores) and 28 threads. Integrated Intel UHD Graphics 770 included
- Up to 5.6 GHz with Turbo Boost Max Technology 3.0 gives you smooth game play, high frame rates, and rapid responsiveness
- Compatible with Intel 600-series (with potential BIOS update) or 700-series chipset-based motherboards
- DDR4 and DDR5 platform support cuts your load times and gives you the space to run the most demanding games
Keyframes, rate control and audio
YouTube recommends constant bitrate (CBR) and a two-second keyframe interval, with a maximum interval of four seconds. Set the GOP/keyframe length in frames to match the frame rate: for example, 120 frames at 60 fps or 60 frames at 30 fps for a two-second interval. The sample below uses 120 frames because it assumes 1080p60. QSV option names and behavior can vary by FFmpeg build and runtime, so confirm the supported rate-control and keyframe options with the local encoder help rather than assuming an option works identically everywhere.
For ordinary SDR, YouTube’s advanced settings specify progressive scan, Rec. 709, 8-bit video, two B-frames and one reference frame. Its guidance lists AAC stereo audio at 44.1 kHz and 128 Kbps. Use settings the source and encoder can actually provide; do not force a format conversion without a reason. YouTube recommends RTMPS, which encrypts the stream to and through Google’s servers. The full current settings guidance is at YouTube’s live encoder settings page.
Rank #3
- Get ultra-efficient with Intel Core Ultra desktop processors that improve both performance and efficiency so your PC can run cooler, quieter, and quicker.
- Core and Threads 24 cores (8 P-cores plus 16 E-cores) and 24 threads. Integrated Intel Graphics included
- Performance Hybrid Architecture Integrates two core microarchitectures, prioritizing and distributing workloads to optimize performance
- Performance Unlocked Up to 5.7 GHz unlocked. 40MB Cache
- Compatibility Compatible with Intel 800 series chipset-based motherboards
Get the YouTube stream key and protect it
- Open YouTube Studio, choose Create, then Go live, and open the stream setup. The precise screen can vary with channel status and YouTube’s interface.
- In the stream settings, copy the stream key and the matching RTMPS server address. If YouTube offers a primary server URL, use that with the key as directed by its interface.
- Keep the key private. Treat it like a password: do not publish it, paste it into a public script repository or include it in a screenshot. If it is exposed, reset it in YouTube Studio before streaming again.
- Store the complete publishing URL in a private environment variable or a protected configuration file, not in an article, shared command history or publicly readable log. The example uses
$YOUTUBE_RTMPS_URLfor that privately stored destination.
Loop a file with FFmpeg and publish it
For a file input, FFmpeg documents -stream_loop -1 as infinite looping. Put it before the relevant -i; -re paces file reading at real-time speed so a file is played out rather than sent as fast as it can be read. The following is an illustrative template for a 1080p60 H.264 source with audio and a 60 fps output. It is not a tested command for every FFmpeg/QSV build. Set YOUTUBE_RTMPS_URL privately to the RTMPS publishing destination and key supplied by YouTube, and confirm supported options locally before unattended use.
ffmpeg -re -stream_loop -1 -i input.mp4
-map 0:v:0 -map 0:a:0?
-c:v h264_qsv -b:v 17M -g 120
-c:a aac -b:a 128k -ar 44100
-f flv "$YOUTUBE_RTMPS_URL"Adapt the command to your source and build
-map 0:v:0selects the first video stream.-map 0:a:0?selects the first audio stream if one exists; the question mark makes that mapping optional. If the file has multiple tracks or you want a different one, inspect the input and map the intended stream explicitly.-b:v 17Mis the YouTube recommended H.264 video bitrate for 1080p60, not a universal default. Change it for the chosen resolution and frame rate using YouTube’s table, and use the local encoder’s documented options to configure CBR. Verify actual output bitrate and stream health in a test.-g 120assumes 60 fps and targets a two-second keyframe interval. At 30 fps, use 60 frames; if the output frame rate differs from the source, set and verify the intended output frame rate and calculate the GOP against that rate.- The example does not resize or filter the input. If you need scaling, deinterlacing or other filters, verify the QSV hardware-frame path or supported conversion flow for your FFmpeg build. FFmpeg’s accelerated QSV transcode path requires support from both decoder and encoder and no filters; do not assume a no-copy hardware path still applies once filters are added.
- If the input lacks audio, omit audio mapping and encoding options as appropriate. If its audio format or channel layout differs, inspect and configure conversion deliberately rather than assuming the sample matches it.
FFmpeg’s command-line documentation describes input options, mapping and loop behavior: FFmpeg documentation. For more on hardware acceleration and supported device flows, consult the same documentation and your installed build’s encoder help.
Recommended Free Tools
Rank #4
- Game Without Compromise. Play harder and work smarter with Intel Core 14th Gen processors
- 20 cores (8 P-cores plus 12 E-cores) and 28 threads. Discrete graphics required
- Up to 5.6 GHz with Turbo Boost Max Technology 3.0 gives you smooth game play, high frame rates, and rapid responsiveness
- Compatible with Intel 600-series (with potential BIOS update) or 700-series chipset-based motherboards
- DDR4 and DDR5 platform support cuts your load times and gives you the space to run the most demanding games
Make the setup suitable for continuous operation
Infinite input looping is not the same as a 24/7 service. The FFmpeg process can exit, the host can reboot, the network can fail, the encoder can lose its device, or YouTube can stop receiving the publishing connection. Use a service manager or other process supervisor appropriate to your operating system, retain logs, alert on process exit or loss of stream health, and decide how an operator will restart the stream and verify it is live.
Preflight and recovery plan
- Run a test long enough to exercise representative video and audio, and confirm the received resolution, frame rate, bitrate and audio in YouTube’s live control room.
- Check YouTube’s stream health while the test is running; do not rely on a successful FFmpeg start message alone.
- Deliberately test the recovery procedure before depending on it: restart the FFmpeg process, reboot the host if appropriate, and test the response to a temporary network interruption.
- Keep the source file available at the same path after a reboot, ensure the machine has adequate cooling and power, and arrange logs and notifications so an unattended failure is visible.
- Use separate supervision and reconnection logic for an RTMP publishing output. FFmpeg’s documented network reconnection options apply to particular network input situations; they do not establish automatic reconnection for an RTMP output. Consult FFmpeg protocol options and test the behavior of your actual setup.
Copyright and YouTube channel considerations
Only stream video and audio you own or have permission to use for this kind of public live broadcast. A license for a song or clip in one context may not cover continuous public streaming or monetization. Review the relevant rights for every item in a playlist, including background music, images and third-party footage; a copyright claim or takedown can interrupt a technically healthy stream. You can use StreamNeo’s copyright safety checklist as a preflight aid, but it does not replace permission from the rights holder or YouTube’s policies.
Best Value
- Game without compromise. Play harder and work smarter with Intel Core 14th Gen processors
- 24 cores (8 P-cores plus 16 E-cores) and 32 threads. Integrated Intel UHD Graphics 770 included
- Leading max clock speed of up to 6.0 GHz gives you smoother game play, higher frame rates, and rapid responsiveness
- Compatible with Intel 600-series (with potential BIOS update) or 700-series chipset-based motherboards
- DDR4 and DDR5 platform support cuts your load times and gives you the space to run the most demanding games
Technical availability does not guarantee that a channel or stream complies with YouTube policy or qualifies for monetization. Repeating pre-recorded material as a live broadcast is distinct from whether the channel’s content is original and eligible under YouTube’s monetization policies. Review YouTube’s current rules before building a channel around a loop, and avoid treating an always-on connection as a shortcut to eligibility.
Common problems and fixes
| Symptom | Likely cause | What to check or do |
|---|---|---|
h264_qsv is unavailable |
The FFmpeg build lacks the encoder, or the installed build does not expose QSV. | Check ffmpeg -hide_banner -encoders; install or build an FFmpeg version with appropriate QSV support, then check the driver and runtime path. |
| QSV device or session initialization fails | Integrated graphics may be disabled, invisible to the OS, unsupported by the current driver/runtime, or unavailable to the FFmpeg process. | Check firmware graphics settings, OS device visibility, permissions and compatible driver/runtime installation. On systems with a discrete GPU, confirm the Intel iGPU was not disabled. |
| YouTube reports a bitrate or connection problem | The selected bitrate may exceed stable upload capacity, or the stream’s rate-control and keyframe settings may not match the intended configuration. | Use a lower supported resolution/bitrate if needed, configure CBR where supported, set a two-second keyframe interval, then test and monitor stream health. |
| Video plays but audio is missing | The source may have no audio stream, or the desired audio track was not mapped. | Inspect the input streams and adjust -map; the sample’s optional audio mapping does not create audio where none exists. |
| FFmpeg stops after an error or network interruption | Looping handles end-of-file, not process supervision or output reconnection. | Inspect logs, test the host-level supervisor and recovery procedure, and verify that YouTube receives the restarted stream. |
| Filters fail or force unexpected copies/conversions | The chosen filter may not support the hardware-frame flow expected by the QSV encoder. | Verify the device and frame-transfer path for the installed FFmpeg build, or use a supported conversion path; test output before deploying. |
Or let it run in the cloud
If you want a YouTube loop without leaving your own computer and connection responsible for it, StreamNeo is a cloud service for keeping uploaded videos live on a YouTube channel. Upload a recording or build a playlist, add your YouTube stream key once, and go live. There is no local FFmpeg process to supervise: the cloud service loops the uploaded video and automatically recovers if YouTube drops the stream.
Quick Recap
- Nothing has to stay on at home; the stream runs from the cloud.
- Each slot streams the uploaded video as made, up to 4K 60 fps, at one flat price per slot rather than quality-based tiers.
- Automatic recovery if YouTube drops the stream.
- The first day is free with no card required; one free day per account.
- The monthly option is $9.99 per month.
Start your free StreamNeo day.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
