How to Fix Common Screen Recording Problems

A screen recording that comes back silent, all black, three gigabytes large, or in a format nothing will open is one of the most frustrating ways to waste ten minutes. The good news is that almost every one of these failures has a small handful of known causes, and most are fixable in under a minute once you know where to look. This guide walks through the five problems people hit most often, why each happens, and the exact step that fixes it on Mac, Windows, and in the browser.

Work through each section as problem, then cause, then fix. If you are not sure which is biting you, start with the symptom table near the end and jump to the matching section.

No audio in the recording

This is the single most common complaint, and it is almost always a permission or source-selection issue rather than a broken file. The first thing to understand is that there are two completely separate audio streams: your microphone (your voice) and system audio (the sound the computer plays — a video, a call, a notification). Tools treat them differently, and missing one does not mean the other is gone.

Microphone permission

If your voice is missing, the recorder probably never got mic access. On macOS, open System Settings > Privacy & Security > Microphone and confirm your browser or recording app is toggled on, then restart that app so the permission takes effect. On Windows, go to Settings > Privacy & security > Microphone and make sure both microphone access and per-app access are enabled. In the browser, the address bar shows a microphone icon — click it and set the site to Allow, then reload.

System audio is a separate setting

If the video you recorded plays back with no sound from whatever was on screen, you captured your screen but not system audio. On the Mac the built-in Cmd+Shift+5 recorder cannot capture internal audio at all without a virtual audio driver — it only records the mic. Windows Game Bar does capture system sound by default. In a browser recorder, system audio comes from a checkbox you have to tick at the moment you pick what to share.

The browser tab-audio toggle

When you record in the browser and choose This Tab or Chrome Tab in the share picker, watch for a small Share tab audio checkbox in the bottom-left of that dialog. It is off by default and easy to miss. Tick it before clicking Share and the tab's sound is included. If you pick Entire Screen instead, the audio checkbox is labelled Share system audio and is only offered on some operating systems — Windows yes, macOS often no.

DRM-protected content

If you are recording a streaming service — Netflix, Disney+, Spotify's video, certain course platforms — the audio (and often the video) is deliberately stripped by digital rights management. This is not a bug you can fix; the platform is enforcing it on purpose. There is no setting that restores it.

The recording is a black screen

A black or blank recording means the capture pipeline grabbed an empty frame instead of the real pixels. There are three usual culprits.

DRM again

The most frequent cause: you are recording protected content. Netflix, Disney+, Amazon Prime Video and similar services force the picture to black during any capture. Nothing on your end changes this. The workaround is simply that you cannot record DRM video — record the non-protected thing you actually need instead.

Hardware acceleration and the GPU

When the source app draws directly to the GPU (common with video players, some games, and browser video), the screen-capture layer can read back a black buffer. The fix is to turn off hardware acceleration in the app you are recording or in the recorder. In Chrome or Edge, go to Settings > System and toggle off Use graphics acceleration when available, then relaunch. Many media players have an equivalent setting; disabling GPU/hardware decoding usually makes the captured frame appear.

Window capture versus full screen

If you chose to capture a single window and that window uses GPU compositing or sits behind another, you can get black where the content should be. Switch the recorder to full screen (or in the browser, choose Entire Screen rather than a specific window) and the black patch usually disappears. On Windows, some browser flags affect this too — if a Chromium browser shows black on window capture, capturing the whole screen is the reliable route.

The file is far too big

A few minutes of screen recording ballooning into hundreds of megabytes or several gigabytes comes down to four levers, in roughly this order of impact.

• Resolution. Recording a 4K display produces roughly four times the data of 1080p. If the viewer will watch at normal size, record or downscale to 1080p.
• Bitrate. This is the amount of data per second. Many recorders default to a high bitrate for safety; halving it often halves the file with little visible difference for screen content, which is mostly flat colour and text.
• Frame rate. A talking-head demo or a slide walkthrough looks identical at 30 fps as at 60 fps but is half the size. Reserve 60 fps for fast motion and gameplay.
• Codec. An H.264 (MP4) or VP9 (WebM) file is dramatically smaller than a raw or lightly compressed capture. If your tool exports something huge, it is likely using an inefficient codec.

The simplest cure after the fact is to compress the finished file rather than re-record. You can drop a recording into Reqo's video compressor, which re-encodes it to an efficient codec and lets you trade a little quality for a much smaller file — typically cutting size by half or more without an obvious drop on screen-recorded content. Compressing afterward is also the right move when someone hands you a file you cannot re-make.

The format is wrong or won't open

You hit this when a recording will not import into your editor, will not upload to a platform, or just will not play. Knowing what each container is for makes the fix obvious.

• MP4 (H.264/H.265). The universal default. It plays everywhere, uploads to every social and video platform, and imports into every editor. When in doubt, you want MP4.
• WebM (VP8/VP9). The format most browser recorders produce because it is what the web's recording API outputs natively. It is excellent for embedding on web pages and is small, but some older editors, PowerPoint, and a few upload forms refuse it.
• MOV. Apple's QuickTime container, the default for macOS screen recordings. It plays perfectly on a Mac and in most editors, but Windows and some web uploaders handle it inconsistently.

If a file will not open or upload, the fix is almost always to convert it to MP4. Run the WebM or MOV through Reqo's video converter to get a clean MP4 that imports and uploads anywhere. Converting also fixes the common case where a browser-recorded WebM refuses to drop into a desktop editor.

Recording is laggy or stutters

Choppy playback or dropped frames usually means the machine could not keep up with capture while also running the thing being recorded. Cause and fix, in order:

• Too high a resolution or frame rate for the hardware. Drop from 4K to 1080p and from 60 fps to 30 fps. This is the biggest single win on a modest laptop.
• Too much running at once. Close other heavy apps and spare browser tabs, especially other video. Encoding competes with everything else for CPU and GPU.
• Software encoding on a weak CPU. If your recorder offers hardware (GPU) encoding, enable it so the CPU is not doing the compression alone.
• Disk too slow. Recording to a nearly full or slow external drive can cause stutter. Record to your fastest internal disk and move the file afterward.

If the stutter is only in the live preview but the saved file is smooth, you can usually ignore it — the preview is the first thing a busy machine sacrifices.

The recording cut off early

A recording that stops on its own before you finished is rarely a crash — it is usually a built-in time limit. Linux's GNOME recorder caps clips at 30 seconds by default. Some free online tools stop you at five or ten minutes to push you toward a paid plan. Free trials of paid apps often impose the same kind of ceiling. Phone recorders can also stop when storage runs out.

The fix depends on the tool: raise GNOME's limit with a gsettings tweak, free up storage on a phone, or use a recorder without a cap. Reqo's screen recorder has no time limit on any plan, so a long webinar or training session records in one unbroken file rather than being chopped into pieces.

Symptom, cause and fix at a glance

Symptom	Likely cause	Fix
No voice in recording	Microphone permission not granted	Enable mic in OS privacy settings and the browser, then restart the app
On-screen video has no sound	System / tab audio not captured	Tick "Share tab audio" in the share picker, or use a tool that captures system audio
Streaming content silent or black	DRM protection	Cannot be recorded; capture non-protected content instead
Whole recording is black	Hardware/GPU acceleration	Disable graphics acceleration in the app or recorder and relaunch
One window records black	Window capture with GPU compositing	Capture the entire screen instead of a single window
File is huge	High resolution, bitrate, frame rate or weak codec	Record at 1080p / 30 fps, or compress to MP4 afterward
File won't open or upload	WebM or MOV not supported by the target	Convert to MP4
Laggy or stuttering	Hardware can't keep up	Lower resolution/fps, close apps, enable GPU encoding
Recording stopped early	Built-in time limit	Use a recorder with no cap, or raise the limit / free up storage

Most of these come back to the same root causes: a permission that was never granted, a checkbox that was never ticked, GPU acceleration reading an empty frame, or a tool quietly imposing a limit. Check those four before you blame the recording itself, and you will fix the great majority of failures in seconds.