To make a prerecorded video file smaller, re-encode a copy with an efficient codec such as HEVC, then reduce its bitrate gradually and check the picture before replacing the original. If you mean less bandwidth during a live stream, configure the live encoder for YouTube’s recommended bitrate instead; if you mean smaller local recordings, lower the recording bitrate or transcode afterward. Those are different jobs: YouTube receives a live encoded stream and transcodes it for viewers.
First decide what needs to be smaller
- Source file on disk: Re-encode a copy to reduce storage needs or upload time. You choose the codec, bitrate, resolution, and frame rate.
- Live upload bandwidth: Set the encoder’s live output to a suitable resolution, frame rate, codec, and bitrate. YouTube’s live settings are the relevant guidance for this case.
- Local recording: Record at a lower bitrate or transcode after recording. Plan file rotation and retention yourself; YouTube does not specify a local recording rotation schedule in the cited guidance.
Bitrate and duration determine encoded size. As a decimal estimate, 1 Mbps sustained for an hour is about 0.45 GB before container overhead. For example, 4 Mbps video plus 128 kbps audio totals 4.128 Mbps, or approximately 1.86 GB per hour. These are calculations from the stated bitrates, not published file-size benchmarks.
How to shrink a prerecorded source file
1. Keep the original and encode a representative copy
Use an encoder that lets you select codec, bitrate, resolution, and frame rate. Start with a short section that reflects the real program: include the most detailed imagery and the most motion. Compare that output with the original on a screen where you can judge visible artifacts. There is no single best bitrate for every video, and YouTube’s live bitrate table is not a recipe for a stored source file.
2. Try an efficient codec if your playback and ingest chain supports it
YouTube’s current live encoder settings list H.264, H.265/HEVC, and AV1, but confirm that your encoder and chosen ingest path accept the codec before committing to it. Google’s HLS ingestion documentation says HEVC generally provides “25% to 50% more data compression at the same video quality compared to H.264.” That is a general codec comparison, not a guaranteed saving for a particular file or encode: results depend on content and encoding settings. See Google’s HLS ingestion guidance.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
3. Lower bitrate in small steps, then inspect the result
Reducing bitrate usually reduces file size, but can make fine detail, gradients, or movement look worse. Static artwork or a low-motion loop may tolerate a lower bitrate than detailed, fast-moving footage. Make incremental changes and review the same representative scenes at full size before encoding the complete program.
4. Reduce resolution or frame rate only when it suits the content
Fewer pixels or frames can reduce the data needed, but the trade-off is less image detail or less-smooth motion. Choose the output that fits the material and intended viewing experience rather than reducing these settings automatically. YouTube’s live recommendations vary by resolution, frame rate, and codec; they do not establish a best archival setting for your source file.
5. Check the full-length output and keep a fallback
Verify that the complete encoded file plays correctly, that its audio remains synchronized, and that it is not truncated. Keep the original until the smaller copy has passed those checks. For an always-on program, also confirm that the playback or streaming setup can loop the chosen file reliably.
Recommended YouTube live settings when the goal is lower upload bandwidth
For live ingest, YouTube recommends constant bitrate (CBR), a 2-second keyframe frequency (no more than 4 seconds), RTMP or RTMPS protocol, and up to 60 fps. The listed video codecs are H.264, H.265/HEVC, and AV1; listed audio codecs are AAC or MP3, with stereo audio at 128 kbps. YouTube recommends RTMPS. These are recommendations, not a claim that every workflow has the same minimum requirement. Use the row matching the resolution, frame rate, and codec you actually send:
Recommended Free Tools
Rank #3
- 【Hardware H.265/H.264 Encoding at 1080P60】Dedicated hardware encoder delivers broadcast-quality 1080P60 streams with H.265/H.264 compression. Reduces bandwidth usage by up to 50% compared to legacy H.264-only solutions, while maintaining crisp, crystal-clear video output.
- 【Broad Protocol Support for IP Distribution】 Supports SRT, RTMP(S), RTSP, UDP, HTTP, HLS, WebRTC, TRTC, Icecast and SHOUTcast — integrate seamlessly with CDNs, surveillance NVRs, IPTV systems and browser-based monitoring dashboards. One device replaces multiple single-purpose streaming boxes.
- 【Browser-Based Setup in Minutes】 Set up in minutes through any browser — no software, drivers or OS compatibility issues. DHCP is enabled by default to prevent IP address conflicts on your network. Note: basic networking knowledge (IP address, RTSP/RTMP configuration) is recommended for advanced streaming setups.
- 【Compact Design with Flexible Deployment】Palm-sized form factor (approx. 90×54×29mm) fits easily behind monitors, on shelves, or in equipment racks. Low power consumption ensures reliable 24/7 operation for live events, remote monitoring, and digital signage.
- 【Professional Audio & OSD Overlay + 1-Year Warranty】 Supports HDMI embedded audio plus external 3.5mm input. Built-in OSD generator adds scrolling text, logos, or timestamps directly to the video stream — ideal for branding, event info, or security labeling. Backed by a 1-year warranty and 24/7 online technical support.
| Live ingest resolution and frame rate | AV1 or HEVC recommended video bitrate | H.264 recommended video bitrate |
|---|---|---|
| 720p30 or 720p60 | 6 Mbps | 8 Mbps |
| 1080p30 | 10 Mbps | 14 Mbps |
| 1080p60 | 12 Mbps | 17 Mbps |
| 1440p30 | 15 Mbps | 21 Mbps |
| 1440p60 | 24 Mbps | 34 Mbps |
These are YouTube’s current recommended live-ingest rates, not upload-video settings or guaranteed ideal settings for every encoder. Check YouTube’s live encoder settings, bitrates, and resolutions for the applicable configuration. Do not substitute YouTube’s separate video-upload encoding recommendations for a live encoder target: the upload recommendations describe a different workflow.
Protect stream stability while reducing bitrate
A bitrate that looks good in a local test can still fail if the internet connection cannot sustain it. YouTube recommends testing representative audio and motion, checking stream health, and leaving 20% spare upload bandwidth. If using primary and backup streams, the connection must have capacity for their combined rates. Run a realistic preflight test before relying on a continuous broadcast. See YouTube’s streaming tips.
Rank #4
Plan local recordings and 24/7 archives separately
Smaller local recordings
Set a lower sustained recording bitrate if your recorder offers that control, or transcode completed recordings. Estimate storage from the total audio and video bitrate multiplied by recording duration, then allow room for container overhead. Check that files are intact and continue growing during long runs; YouTube advises validating local archive integrity but does not prescribe a rotation schedule.
Do not rely on one YouTube archive for a stream longer than 12 hours
YouTube says streams under 12 hours can be automatically archived; a stream that exceeds 12 hours may not be captured at all. If preserving the whole program matters, retain a local recording or plan shorter sessions and verify the resulting archives. See YouTube’s live stream archive guidance.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsBest Value
Common problems and fixes
- The smaller file looks blocky or smeared: The bitrate may be too low for the scene’s detail or motion. Re-encode a representative segment at a higher bitrate, or retain more resolution or frame rate.
- The encoder rejects the codec: The encoder or selected ingest path may not support that codec. Confirm the supported ingest settings, then use a compatible option such as H.264 if needed.
- The live stream buffers or loses health: The connection may lack sustained upload capacity or headroom. Check the connection with a speed test, reduce the live output to a suitable recommended rate, preserve the 20% bandwidth margin, and run a preflight test.
- The file is smaller, but the live stream still uses too much bandwidth: Source-file size and live upload rate are different measures. Configure the live encoder’s output bitrate rather than assuming a smaller stored file automatically lowers the live stream rate.
- A long broadcast is missing from the channel archive: An automatic archive is not assured for a stream beyond 12 hours. Use and check a local recording or divide the broadcast into shorter sessions if separate archives are needed.
Or let it run in the cloud
StreamNeo keeps an uploaded video or playlist live on YouTube from the cloud, so your computer and home connection do not have to stay on. Upload your recording, add your YouTube stream key once, and go live. It streams the file as uploaded, up to 4K 60fps, at one flat price per slot; automatic recovery can restart the stream if YouTube drops it. The first day is free with no card. Monthly pricing is $9.99 per month. Learn more at StreamNeo, or start your free day.
Quick Recap
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.
