Hearthstone

Complete OBS Studio capture guide for Hearthstone: best capture method, audio routing, starting settings, performance, black screen fixes, privacy, troubleshooting, and FAQ.

Best: Window Capture

This OBS-Studio.net editorial guide covers Hearthstone OBS guide. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Overview

This complete guide explains how to capture Hearthstone in OBS Studio with a reliable primary method and a fallback. It focuses on verification steps rather than copying unverified presets.

Regarding Overview: For Hearthstone OBS guide, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Overview: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Overview: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Overview: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Overview: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Overview: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Overview: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Overview: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Recommended capture

Start with Window Capture for Hearthstone. If that fails after a clean test, fall back to Display Capture and compare Stats dock counters under identical load.

Regarding Recommended capture: For Hearthstone OBS guide, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Recommended capture: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Recommended capture: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Recommended capture: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Recommended capture: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Recommended capture: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Recommended capture: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Recommended capture: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Scene layout

Keep HUD-critical regions clear of webcam and alert overlays. Build a gameplay/application scene, a break scene without the capture, and a chatting scene if you need it.

Regarding Scene layout: For Hearthstone OBS guide, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Scene layout: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Scene layout: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Scene layout: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Scene layout: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Scene layout: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Scene layout: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Scene layout: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Download statistics and community rating counts are intentionally omitted. Prefer official project pages and GitHub releases. This page does not claim measured benchmark FPS for hardware. Re-check platform bitrate and codec limits on the destination site before a public broadcast.

Audio routing

This OBS-Studio.net editorial guide covers Hearthstone audio routing. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Desktop vs application audio

Route Hearthstone audio separately from voice when your OS supports application audio capture. This protects VODs and makes balancing easier.

Regarding Desktop vs application audio: For Hearthstone audio routing, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Desktop vs application audio: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Desktop vs application audio: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Desktop vs application audio: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Desktop vs application audio: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Desktop vs application audio: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Desktop vs application audio: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Desktop vs application audio: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Voice chat

If Hearthstone includes voice chat, place it on its own track where possible so you can mute it in recordings without removing your microphone.

Regarding Voice chat: For Hearthstone audio routing, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Voice chat: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Voice chat: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Voice chat: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Voice chat: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Voice chat: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Voice chat: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Voice chat: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Monitoring

Monitor in headphones to avoid echo. Disable exclusive mode on Windows devices that block OBS from sharing the endpoint.

Regarding Monitoring: For Hearthstone audio routing, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Monitoring: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Monitoring: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Monitoring: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Monitoring: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Monitoring: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Monitoring: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Monitoring: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Starting settings

This OBS-Studio.net editorial guide covers Hearthstone starting settings. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Video

Match canvas to your monitor or the resolution you intend to stream. Cap the game frame rate to leave GPU headroom for compositing.

Regarding Video: For Hearthstone starting settings, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Video: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Video: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Video: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Video: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Video: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Video: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Video: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Output

Use a hardware encoder when available for live output. Prefer CBR for streaming and CQP/CRF-style controls for local recordings.

Regarding Output: For Hearthstone starting settings, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Output: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Output: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Output: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Output: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Output: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Output: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Output: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Capture properties

Set Window Capture explicitly: pick the correct window/game, disable unnecessary compatibility hooks first, and only enable them if the capture stays black.

Regarding Capture properties: For Hearthstone starting settings, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Capture properties: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Capture properties: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Capture properties: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Capture properties: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Capture properties: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Capture properties: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Capture properties: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Performance

This OBS-Studio.net editorial guide covers Hearthstone performance. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Headroom

A saturated GPU causes rendering lag even with NVENC/AMF. Cap FPS in Hearthstone below the sustained maximum.

Regarding Headroom: For Hearthstone performance, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Headroom: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Headroom: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Headroom: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Headroom: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Headroom: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Headroom: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Headroom: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Overlays

Close third-party overlays that hook the same graphics APIs. Test with a clean capture before blaming OBS.

Regarding Overlays: For Hearthstone performance, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Overlays: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Overlays: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Overlays: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Overlays: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Overlays: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Overlays: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Overlays: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Measurement

Use the Stats dock during typical Hearthstone action — menus are not representative. This guide does not publish fabricated FPS benchmark tables.

Regarding Measurement: For Hearthstone performance, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Measurement: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Measurement: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Measurement: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Measurement: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Measurement: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Measurement: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Measurement: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Black screen

This OBS-Studio.net editorial guide covers Hearthstone black screen fixes. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

GPU mismatch

On dual-GPU machines, run OBS and Hearthstone on the same GPU for Game Capture, or use Display Capture on the correct display.

Regarding GPU mismatch: For Hearthstone black screen fixes, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding GPU mismatch: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding GPU mismatch: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding GPU mismatch: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding GPU mismatch: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding GPU mismatch: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding GPU mismatch: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding GPU mismatch: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Permissions

On macOS grant Screen Recording; on Windows try running both elevated or both normal, not mixed.

Regarding Permissions: For Hearthstone black screen fixes, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Permissions: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Permissions: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Permissions: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Permissions: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Permissions: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Permissions: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Permissions: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Fallback

If Window Capture remains black after updates, switch to Display Capture temporarily and retest after driver or game patches.

Regarding Fallback: For Hearthstone black screen fixes, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Fallback: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Fallback: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Fallback: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Fallback: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Fallback: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Fallback: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Fallback: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Privacy

This OBS-Studio.net editorial guide covers Hearthstone privacy. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Display Capture risks

Display Capture shows notifications and other windows. Prefer Window Capture when it works.

Regarding Display Capture risks: For Hearthstone privacy, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Display Capture risks: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Display Capture risks: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Display Capture risks: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Display Capture risks: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Display Capture risks: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Display Capture risks: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Display Capture risks: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Account safety

Hide emails, friend lists, and stream keys. Use a BRB scene that removes the game capture entirely.

Regarding Account safety: For Hearthstone privacy, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Account safety: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Account safety: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Account safety: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Account safety: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Account safety: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Account safety: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Account safety: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Chat and personal data

Blur or crop regions that may reveal personal information inside Hearthstone.

Regarding Chat and personal data: For Hearthstone privacy, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Chat and personal data: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Chat and personal data: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Chat and personal data: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Chat and personal data: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Chat and personal data: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Chat and personal data: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Chat and personal data: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Troubleshooting

This OBS-Studio.net editorial guide covers Hearthstone troubleshooting. It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Audio missing

Confirm the correct device meters move. Re-select application audio captures after restarting Hearthstone.

Regarding Audio missing: For Hearthstone troubleshooting, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Audio missing: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Audio missing: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Audio missing: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Audio missing: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Audio missing: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Audio missing: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Audio missing: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Stutter

Check rendering lag vs encoding lag vs network drops separately — each needs a different fix.

Regarding Stutter: For Hearthstone troubleshooting, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Stutter: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Stutter: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Stutter: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Stutter: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Stutter: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Stutter: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Stutter: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Crashes

Safe Mode, clean profile, then add the Hearthstone capture alone before restoring overlays and plugins.

Regarding Crashes: For Hearthstone troubleshooting, keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Crashes: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Crashes: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Crashes: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Crashes: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Crashes: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Crashes: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Crashes: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

FAQ

Best capture for Hearthstone?: Window Capture first, then Display Capture.
Should I use Display Capture?: Only as a fallback — it is less private and often heavier.
Why is the preview lagging?: Check Stats for rendering lag and reduce GPU load in Hearthstone.