		<div class="wpcnt">
			<div class="wpa">
				<span class="wpa-about">Advertisements</span>
				<div class="u top_amp">
							<amp-ad width="300" height="265"
		 type="pubmine"
		 data-siteid="173035871"
		 data-section="1">
		</amp-ad>
				</div>
			</div>
		</div><p dir="ltr">For roughly a decade, recording your Mac&#8217;s internal audio meant installing a virtual driver like BlackHole or Soundflower, digging into Audio MIDI Setup, building a Multi-Output Device, and hoping the whole fragile chain didn&#8217;t break on the next macOS update. That workaround still works, and plenty of current guides still walk through it step by step. It&#8217;s also no longer necessary for most people, because Apple quietly added native system audio capture to macOS, and free tools have already built support for it.</p>
<h2 dir="ltr">Why Mac Audio Recording Got a Reputation for Being Painful</h2>
<p dir="ltr">Apple&#8217;s built-in tools, Cmd+Shift+5 for screen recording and QuickTime Player, have never captured system audio on their own. They record your microphone, and that&#8217;s it. For years, the only way around that limitation was routing your Mac&#8217;s audio output through a virtual driver so a recording app could pick it up as if it were an input device, a process that felt more like a systems administration task than something a normal user should have to do for a basic screen recording. That difficulty is exactly why BlackHole became the default recommendation everywhere, not because it was elegant, but because it was the only free option that worked.</p>
<h2 dir="ltr">What Actually Changed</h2>
<p dir="ltr">Apple&#8217;s ScreenCaptureKit framework, refined across recent macOS releases, now supports capturing system audio directly, without any virtual driver, kernel extension, or manual routing. Developers building recording tools have adopted this framework specifically to let their apps capture internal audio natively, which means the fix for most people isn&#8217;t a manual workaround anymore, it&#8217;s simply picking a tool that already uses Apple&#8217;s modern audio capture API instead of asking you to build your own audio pipeline by hand.</p>
<p dir="ltr">That&#8217;s a meaningful shift. The problem was never that macOS couldn&#8217;t technically support this. It&#8217;s that Apple restricted the capability for privacy and security reasons for years before opening a proper, sanctioned path for developers to use it.</p>
<h2 dir="ltr">The Free Way: OBS Studio</h2>
<p dir="ltr">OBS Studio is free, open source, and already built around Apple&#8217;s modern audio capture framework, making it the strongest genuinely free option for anyone comfortable with a slightly more feature-rich interface than a bare screen recorder. Download it from the official OBS Project website, and on first launch, grant the Screen Recording and Microphone permissions macOS prompts for in System Settings under Privacy and Security.</p>
<p dir="ltr">To capture system audio specifically, add a new audio source in OBS and select the system audio capture option rather than a microphone input. This routes your Mac&#8217;s output, app sounds, browser audio, a video call, directly into your recording without touching Audio MIDI Setup or installing anything beyond OBS itself. Because OBS runs without kernel extensions, it works cleanly on current Apple Silicon Macs without the driver-compatibility issues that periodically broke BlackHole after a macOS update.</p>
<h2 dir="ltr">The Simplest Way: Dedicated Recording Apps</h2>
<p dir="ltr">If OBS feels like more tool than you need for a quick recording, a newer generation of lightweight, purpose-built apps has emerged specifically to make this a two-click process. Apps like Cap are built natively around system audio capture, with no routing and nothing to configure beyond toggling system audio on before you hit record. After granting the same Screen Recording and Microphone permissions macOS always requires, you switch an audio control from &#8220;No System Audio&#8221; to &#8220;Record System Audio,&#8221; and that&#8217;s the entire setup.</p>
<p dir="ltr">These apps typically separate your microphone and system audio into distinct tracks automatically, which is genuinely useful for editing afterward, letting you balance a quiet voiceover against louder app audio independently rather than fighting with a single merged track the way the old BlackHole method often produced.</p>
<h2 dir="ltr">If You Still Want to Use BlackHole</h2>
<p dir="ltr">There&#8217;s a legitimate reason some people still reach for BlackHole: audio professionals who need multi-channel routing, custom aggregate devices combining several inputs, or workflows built around specific digital audio workstation software may still need that level of manual control. If that&#8217;s you, the process remains the same as it always has: install BlackHole, open Audio MIDI Setup, create a Multi-Output Device combining BlackHole with your regular speakers so you can still hear audio while it&#8217;s being captured, switch your Mac&#8217;s sound output to that combined device, then select BlackHole as your input in QuickTime Player or another recording app.</p>
<p dir="ltr">The catch worth knowing going in: this method requires building a separate Aggregate Device if you want to combine your microphone and system audio into a single recording, since QuickTime only accepts one input device at a time. Level balancing between the two sources, and occasional drift between them, becomes your problem to manage manually. For anyone who doesn&#8217;t specifically need that level of manual audio routing control, it&#8217;s genuinely more setup than the native alternatives above require for the same practical result.</p>
<h2 dir="ltr">What About Preview and QuickTime Alone?</h2>
<p dir="ltr">It&#8217;s worth being direct about this since it trips people up constantly: neither Preview nor a standalone QuickTime recording, without BlackHole or a similar driver, will ever capture your Mac&#8217;s internal audio. This isn&#8217;t a bug or a setting you&#8217;re missing. Apple&#8217;s own built-in tools simply were never built with that specific capability, and no amount of digging through QuickTime&#8217;s menus will reveal a hidden system-audio toggle. If you want internal audio without third-party software, OBS Studio remains the only fully native-feeling, genuinely free path available right now.</p>
<h2 dir="ltr">Step-by-Step: The Fastest Free Method</h2>
<p dir="ltr">Download and install OBS Studio from obsproject.com. On first launch, approve both Screen Recording and Microphone permissions when macOS prompts you, found under System Settings, Privacy and Security if you need to grant them manually afterward. Create a new Scene, then add a Display Capture source for your screen and a separate Audio Output Capture source for system audio. Add an Audio Input Capture source as well if you also want your microphone recorded alongside system sound. Hit Start Recording, and OBS will capture your screen, your Mac&#8217;s internal audio, and your microphone as separate, adjustable tracks, with no virtual driver and no Audio MIDI Setup involved at any point.</p>
<h2 dir="ltr">Common Problems and How to Actually Fix Them</h2>
<p dir="ltr">The most frequent OBS issue on Mac is a recording that completes with a visibly moving audio meter during capture but plays back silent. That almost always means the audio source was added but never actually assigned as an input in the scene&#8217;s mixer, rather than a permissions failure. Check that the Audio Output Capture source shows activity in OBS&#8217;s own audio mixer panel before you start recording, not just after, since a silent meter at that stage means the source needs to be reconfigured before you waste time on a full recording.</p>
<p dir="ltr">Permission prompts that seem to disappear without granting access are the second common snag. If OBS or a dedicated recording app isn&#8217;t capturing screen content or audio despite you clicking &#8220;allow,&#8221; check System Settings, Privacy and Security, Screen Recording and Microphone directly, since macOS sometimes requires a full app restart after permissions are granted before the change actually takes effect, not just a re-attempt within the same session. Quitting and reopening the app after granting permissions resolves this far more often than repeating the same recording attempt.</p>
<p dir="ltr">If you&#8217;re specifically trying to capture audio from a single application rather than everything playing on your Mac, standard system audio capture grabs all system output indiscriminately, not just one app&#8217;s sound. For that more targeted use case, OBS&#8217;s per-application audio capture option, where supported, or manually muting other audio sources before recording, gets you closer to an isolated result than system-wide capture alone.</p>
<h2 dir="ltr">When You&#8217;d Actually Want More Than the Basic Free Method</h2>
<p dir="ltr">The native, no-driver approach above covers the overwhelming majority of use cases, tutorials, reaction videos, capturing a video call, recording a demo. There are a few situations where the extra complexity of BlackHole or a paid tool genuinely earns its place instead. Podcast or music production workflows that need to route audio between several specialized applications, not just capture what&#8217;s playing, benefit from BlackHole&#8217;s flexibility as a general-purpose virtual audio cable rather than a single-purpose recording feature. Teams recording the same kind of content daily, client demos, onboarding videos, support walkthroughs, may find a paid, purpose-built tool&#8217;s reliability across macOS updates worth the cost, since free driver-based solutions have a documented history of breaking after major system updates until a compatible new version ships.</p>
<p dir="ltr">For nearly everyone else, doing a single recording, a handful of tutorials, or the occasional reaction video, the free, native path through OBS Studio or a similar modern app is genuinely sufficient, and reaching for a more complex or paid solution first is solving a problem you probably don&#8217;t have yet.</p>
<h2 dir="ltr">Common Questions About Recording Internal Audio on Mac</h2>
<h3 dir="ltr"><strong>Why doesn&#8217;t QuickTime just record internal audio by default?</strong></h3>
<p dir="ltr">Apple&#8217;s built-in screen and audio recording tools were never built to capture system output, only microphone input, largely due to longstanding privacy and security restrictions around audio capture. That limitation hasn&#8217;t changed, which is why any internal-audio solution runs through a separate tool rather than a hidden QuickTime setting.</p>
<h3 dir="ltr"><strong>Is OBS Studio actually free, with no watermark or limits?</strong></h3>
<p dir="ltr">Yes. OBS Studio is fully open source and free with no watermarks, time limits, or feature restrictions of any kind. Its learning curve is slightly steeper than a single-purpose recording app, but there&#8217;s no cost involved at any tier.</p>
<h3 dir="ltr"><strong>Do I still need BlackHole for anything in 2026?</strong></h3>
<p dir="ltr">Mainly for advanced, multi-channel professional audio routing or specific digital audio workstation workflows that need more granular control than a standard system-audio-capture tool provides. For a typical screen recording, tutorial, or reaction video, native system audio capture through OBS or a similar modern app covers the need without it.</p>
<h3 dir="ltr"><strong>Will this native audio capture method work on an older Intel Mac?</strong></h3>
<p dir="ltr">Apple&#8217;s ScreenCaptureKit framework and the native audio capture built on top of it require a reasonably current macOS version rather than being tied specifically to Apple Silicon. Very old Intel Macs running outdated macOS versions may need to stay with the BlackHole method if they can&#8217;t update to a macOS release that supports the modern framework.</p>
<h2 dir="ltr">The Bottom Line</h2>
<p dir="ltr">If a guide you&#8217;re reading walks you through BlackHole, Audio MIDI Setup, and building a Multi-Output Device as the only free option, it&#8217;s describing a workaround that Apple&#8217;s own modern audio framework has largely made unnecessary. Start with OBS Studio or a similarly native-feeling free app instead, and save the manual driver routing for the specific, advanced audio workflows that genuinely still need it.</p>
<h2 dir="ltr"><strong>References and Sources</strong></h2>
<p dir="ltr">Cap, &#8220;How to Screen Record on a Mac With Audio (System Sound + Mic), Free in 2026&#8221;: <a href="https://cap.so/blog/record-screen-mac-system-audio">https://cap.so/blog/record-screen-mac-system-audio</a></p>
<p dir="ltr">Cubix, &#8220;How to Record System Audio on Mac (Without BlackHole)&#8221;: <a href="https://cubix.design/resources/how-to-record-system-audio-on-mac-without-blackhole">https://cubix.design/resources/how-to-record-system-audio-on-mac-without-blackhole</a></p>
<p dir="ltr">Bandicam, &#8220;How to Record Internal Audio on Mac (System Audio Guide)&#8221;: <a href="https://www.bandicam.com/blog/how-to-record-internal-audio-on-mac/">https://www.bandicam.com/blog/how-to-record-internal-audio-on-mac/</a></p>
<p dir="ltr">ScreenSnap, &#8220;How to Screen Record with Audio on Mac (2026 Guide)&#8221;: <a href="https://www.screensnap.pro/blog/screen-record-with-audio-mac">https://www.screensnap.pro/blog/screen-record-with-audio-mac</a></p>
<p dir="ltr">Muhammad Karim, &#8220;How to Record Internal Audio on a Mac, With or Without a Mic&#8221;: <a href="https://www.mkarim.us/blog/2026-09-01-record-internal-audio-mac.html">https://www.mkarim.us/blog/2026-09-01-record-internal-audio-mac.html</a></p>

How to Record Internal Audio on Mac Free (No BlackHole Needed)
How to Record Internal Audio on Mac Free (No BlackHole Needed)