If your Raspberry Pi plays a YouTube playlist in a browser over the internet, its storage card does not need to contain a day’s worth of video. You need space for the operating system, playback software, and any files or data you choose to keep on the Pi.
For a browser-based setup, Raspberry Pi’s current starting recommendation is at least 32 GB for Raspberry Pi OS with desktop. If you store video files locally instead, calculate their size from their actual bitrate and runtime, then add the operating system and room for other data.
First decide whether video is streamed or stored
A playlist playing on YouTube in a browser is online playback. The Pi receives the video as it plays; the playlist’s total runtime is not the amount of video saved on its microSD card. If the playlist runs for 24 hours and repeats, that does not mean you need 24 hours of video files on the card.
The card still holds the operating system and installed applications. The browser may use some local cache while playing, but the official Raspberry Pi material cited here does not give a fixed cache size for a round-the-clock YouTube setup. Do not treat an unknown or variable browser cache as a local copy of the playlist.
Local playback is a different arrangement. You keep video files on the card or another attached storage device and use software to play those files. In that case, media capacity depends on the files themselves: their bitrate, duration, and number. A playlist made from several stored clips needs enough room for all the clips you intend to retain, not just for one clip playing at a time.
This distinction also matters if you are thinking of downloading videos through YouTube. YouTube’s offline viewing help and offline videos FAQ describe features subject to conditions such as eligibility, account, region, device, and video availability. They do not establish a general way to save any playlist as ordinary video files for a Raspberry Pi. Check the current official terms and available features rather than assuming an offline download is a transferable file.
Start with the operating-system recommendation
Raspberry Pi’s getting-started documentation recommends at least 32 GB for Raspberry Pi OS desktop editions and at least 8 GB for Raspberry Pi OS Lite. These are boot-media recommendations for the operating system, not measurements of YouTube video storage or guarantees that a particular playback arrangement will work.
For a browser kiosk, the desktop figure is the more useful starting point. A desktop edition includes the graphical environment needed for a browser window, whereas Lite is a lighter operating-system option intended for setups that do not require a desktop. If your plan depends on opening a browser directly on the Pi, begin with the 32 GB recommendation rather than treating the 8 GB Lite baseline as a browser-ready capacity target.
Raspberry Pi’s documentation also says SD cards below 2 TB are supported. That is a compatibility statement, not a reason to buy a very large card for streamed playback. A 64 GB card may be a sensible purchase if it is readily available or if you expect to retain files, but the playlist’s daily runtime by itself does not justify it.
| Setup | Storage starting point | What the figure means |
|---|---|---|
| Raspberry Pi OS with desktop for browser playback | At least 32 GB | Raspberry Pi’s OS boot-media recommendation; playlist video is streamed |
| Raspberry Pi OS Lite | At least 8 GB | Lighter OS baseline, not a claim that a browser kiosk fits or that video storage is included |
| Local video files | Calculated from files | Add the media estimate to the OS and other retained data |
These figures come from Raspberry Pi’s documentation, current at the time of writing. They are not guarantees about free space after installation: OS version, applications, updates, and retained data affect what remains available. For the difference between a Pi and a small computer in a playlist-streaming role, see our comparison of a Raspberry Pi 4 and refurbished mini PC for a Hindi playlist stream.
Calculate storage for files kept locally
If you have actual video files, a transparent estimate is:
Decimal GB ≈ bitrate in Mb/s × duration in hours × 0.45
The multiplier converts megabits per second over hours into an approximate decimal gigabyte total. It is a planning calculation, not a claim about typical YouTube file sizes. For a more accurate estimate, use the file sizes shown by your file manager or add the sizes of the exact files you plan to keep.
For example, a file encoded at 1 Mb/s and lasting one hour works out to approximately 0.45 GB. Ten hours at that bitrate would be about 4.5 GB. At 5 Mb/s, ten hours would be about 22.5 GB. These examples illustrate the arithmetic only; they do not describe a universal YouTube quality setting, a standard encoding, or what a particular playlist will use.
A playlist may have files with different bitrates and runtimes. If you know each file’s bitrate and duration, calculate each one and add the results. If you do not know those values, the visible file sizes are usually the most direct inventory: add the sizes of all files to be retained, then leave room for the operating system and anything else stored on the device.
Bitrate is only useful for this estimate when it represents the video file you actually possess or plan to create. Do not take an advertised stream quality, multiply it by 24 hours, and treat the result as the exact size of a YouTube playlist. Online playback does not create a day-long local archive, and the calculation cannot infer the size of files that you have not measured.
Compare a day of files with a day of streaming
A 24-hour local collection at 1 Mb/s works out to about 10.8 GB using the formula above. At 5 Mb/s, the same 24 hours works out to about 54 GB. Those are arithmetic examples for hypothetical locally stored video, not estimates of any particular YouTube playlist or its download size.
The practical difference is clear: a Pi streaming an online playlist needs the OS and working storage, while a Pi playing a locally stored day-long set needs capacity for those files as well. If you want a local loop, add up the retained clips rather than assuming one day’s playlist duration maps to a standard card size. A locally stored set could be smaller or larger depending on its bitrate and contents.
| Hypothetical local media bitrate | Runtime | Approximate media space |
|---|---|---|
| 1 Mb/s | 24 hours | 10.8 GB |
| 5 Mb/s | 24 hours | 54 GB |
| 1 Mb/s | 48 hours | 21.6 GB |
The figures use decimal GB and the stated approximation. Real file sizes can differ because files may have variable bitrates, audio tracks, container overhead, or different encodings. If the local files already exist, trust their combined file size over a calculated estimate.
For mixed use, add the local media total to the OS starting point, software, and other retained data. A 32 GB card is not automatically enough just because it meets the desktop OS recommendation: if your local files take most of its capacity, there may be little room left for updates or additional files. Conversely, if you only stream online and retain little data, the full runtime of the playlist does not need to be added to the card calculation.
Account for software, cache, and retained data separately
Think of capacity in separate buckets: operating system, playback applications, locally retained media, and other data. The OS recommendation is a starting point for the boot medium, not a promise about the remaining free space after you configure the Pi. Browser installation, updates, logs, downloads, screenshots, or unrelated files can consume additional capacity.
A browser can use cache while loading and playing content. The amount depends on the browser, settings, OS, and playback behaviour; the official sources reviewed for this article do not specify a fixed cache allowance for 24/7 YouTube playback on a Pi. It is therefore better to monitor available space after setup than to invent a universal cache figure. If space steadily falls, investigate retained downloads and other data rather than presuming that the playlist is being stored in full.
Leave room for updates and normal use, but no exact universal buffer is specified in the sources cited here. A card with no free capacity can make routine maintenance awkward even when the original OS installation fitted. If you intend to store locally encoded video, keep that media on a separate USB drive if the arrangement suits your Pi and playback software; capacity for the boot card and capacity for the media do not have to be the same purchase.
Before copying a large collection, inspect the files’ actual sizes and confirm that your playback software can read them. The relevant question is not simply “How many hours?” but “How many bytes of files will remain on this device?” For online playback, also remember that an internet connection is part of the arrangement. A locally stored collection may be useful where connectivity is unreliable, but it introduces file management and a larger storage requirement.
Choose Desktop or Lite around the playback method
A browser-based YouTube playlist normally points towards Raspberry Pi OS with desktop, because a graphical browser is part of the setup. Raspberry Pi’s kiosk-mode tutorial describes a graphical web-browser kiosk and specifies a Raspberry Pi 3 or newer with at least 1 GB of RAM for that tutorial. That guidance is useful context for a browser arrangement, but it does not promise continuous YouTube playback reliability or define a card size for every configuration.
Lite is relevant if your system is deliberately headless or uses a playback method that does not require a desktop environment. Its 8 GB figure is the Lite OS recommendation, not a shortcut that automatically makes a browser kiosk suitable. Confirm that your chosen player and setup work without the graphical desktop before selecting Lite solely to reduce the operating-system footprint.
Neither OS choice changes the arithmetic for local media. If you retain video files, calculate their space independently and add it to the relevant OS baseline. Likewise, choosing desktop does not mean the Pi downloads the playlist: browser playback remains online unless you separately create a local-file workflow.
If your aim is a screen that simply shows YouTube content, the lake ambience live-stream example may help clarify the distinction between a video presented as a live stream and a Pi playing a playlist locally. If your actual need is to keep a prepared broadcast running without leaving a personal computer switched on, StreamNeo removes that particular machine-running burden by turning an uploaded video into a YouTube live stream, rather than using the Pi as the playback device.
Make the card choice from the files you will keep
For a straightforward online playlist in a browser, start from the 32 GB desktop recommendation and decide whether you want extra space for other local use. The playlist’s 24-hour duration does not require 24 hours of video capacity. For a headless arrangement using Lite, Raspberry Pi’s 8 GB recommendation is an OS baseline; check the playback method and retained data before settling on a card.
For a local-file loop, total the files you plan to retain. If the videos are not yet encoded, estimate each from its bitrate and runtime, or use the combined file size once you have the files. Add space for the operating system and other data, and choose capacity with enough remaining room for routine use. The exact card capacity depends on those actual files, not on a universal notion of a “day of YouTube”.
The internal guide to playing Indian music videos from multiple folders with OBS is relevant if your question is really about a local library feeding a broadcast, rather than a Pi browsing a YouTube playlist. These are different jobs: one plays online content on a Pi, another uses stored media in a broadcast workflow. Keep the storage estimate tied to the job you intend to run.
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 a Raspberry Pi save streamed YouTube videos to its SD card?
Not as a day-long set of ordinary video files merely because you play a playlist in a browser. The browser may use cache, but the official guidance cited here does not state a fixed cache size for this setup. Treat the card as OS, software, and intentionally retained data, not as a full playlist archive.
Is 32 GB enough for a 24/7 online playlist?
Raspberry Pi recommends at least 32 GB for Raspberry Pi OS desktop, which is the more relevant starting point for browser playback. That recommendation is for the operating system boot medium, not a guarantee about every setup or about space left after installing software and retaining files. The playlist duration itself does not add 24 hours of video to the card.
Should I use a 64 GB card instead?
A larger card can be useful if you plan to keep local media, install other software, or retain other files. For online playback alone, the day-long playlist is not a reason to assume you need 64 GB. Choose according to your OS, actual local files, and the free room you want for normal use.
How do I know the size of a local 24-hour playlist?
Add the actual sizes of all the files you intend to keep. If you only know bitrate and duration, use decimal GB ≈ Mb/s × hours × 0.45 as a planning estimate; for example, 24 hours at 1 Mb/s is about 10.8 GB. This is a calculation for hypothetical local files, not a claim about a YouTube playlist’s universal file size.