The best OBS settings for streaming Minecraft are 1920×1080 at 60 fps, 6,000 kbps CBR on your GPU’s hardware encoder and a 2-second keyframe interval for Twitch, but slow building streams often look sharper at 1080p and 30 fps, and the right capture source depends on whether you play Java or Bedrock. Minecraft is unusual because the same game can be a calm creative build or a frantic Bedwars match, so pick your output by stream style first, then fix capture and in-game settings.
Top 3 picks at a glance
Match the output to the kind of Minecraft you stream
All rows use CBR, a 2-second keyframe interval and 160 kbps AAC audio. Bitrates are Twitch figures unless noted; Twitch’s guideline is 6,000 kbps for 1080p60, 4,500 kbps for 1080p30 or 720p60 and 3,000 kbps for 720p30.
| Stream style | Output resolution | FPS | Video bitrate | Why |
|---|---|---|---|---|
| Survival, building, redstone | 1920×1080 | 30 | 4,500–6,000 kbps | Slow camera, viewers study block detail |
| Let’s play with regular combat | 1920×1080 | 60 | 6,000 kbps | Smooth turns matter more than texture detail |
| PvP minigames, Bedwars, duels | 1600×900 | 60 | 6,000 kbps | Fast flicks refill the whole frame with new detail |
| Elytra travel, speedruns | 1664×936 | 60 | 6,000 kbps | New terrain streams in every second |
| Shader showcase | 1920×1080 (2560×1440 on YouTube) | 60 | 6,000 kbps Twitch; 12,000–20,000 kbps YouTube AV1 or HEVC | Fog, bloom and water reflections are costly to encode |
| Older laptop or integrated graphics | 1280×720 | 30 | 3,000 kbps | Leaves the GPU free for the game |
The 30 fps recommendation for building streams comes from simple arithmetic. At 1080p60 and 6,000 kbps, each pixel gets about 0.048 bits per frame (6,000,000 divided by 124.4 million pixels per second). At 1080p30 and 4,500 kbps, that rises to about 0.072 bits per pixel, 50% more, and at 1080p30 with the full 6,000 kbps it doubles to about 0.096. On a slow pan across a detailed build, that extra data shows up as cleaner textures. Once you start sprinting, fighting or flying, 60 fps wins.
Java vs Bedrock: getting a clean capture
Java Edition
- Add a Game Capture source, choose Capture specific window and select the javaw.exe entry whose title starts with Minecraft. Game Capture works in windowed mode too, so you don’t have to play fullscreen (F11 toggles it).
- On laptops with hybrid graphics, the Java runtime can launch on the integrated GPU while OBS runs on the dedicated one, which gives a black Game Capture. In Windows Settings, System, Display, Graphics, add the javaw.exe that the launcher uses (it lives in the launcher’s runtime folder) and obs64.exe, and set both to High performance.
- Third-party launchers and modpack managers often use their own Java install, so repeat that step for the javaw.exe they point to.
Bedrock Edition
- Game Capture usually hooks Minecraft.Windows.exe directly. If it stays black, use Window Capture with the capture method set to Windows 10 (1903 and up), which grabs the window through Windows itself rather than hooking the game.
- Bedrock’s Vibrant Visuals mode and ray-traced resource packs push the GPU much harder than the default look. Cap the frame rate with your GPU driver’s limiter so OBS keeps some headroom.
Why blocky textures are harder to encode than they look
Minecraft looks simple, but its 16×16 textures are drawn with hard pixel edges, and every block boundary is a sharp, high-contrast line. Sharp edges cost bits. Distant textures also shimmer as you move, which the encoder sees as fresh noise every frame. Three settings keep this under control:
- Mipmap Levels: Leave it at 4 in Video Settings. Setting it to 0 makes distant blocks look crisper on your monitor but turns them into flickering noise that eats bitrate on stream.
- Downscale Filter: If your output is smaller than your canvas, choose Lanczos in Settings, Video. Bilinear blurs block edges into a smeary look; Lanczos keeps them defined.
- Source scaling: Best practice is to run the game at your canvas resolution so OBS doesn’t rescale it at all. If you must enlarge a small game window, the Point scale filter keeps blocks razor-sharp only at exact 2x scaling; at other ratios, use Lanczos or Bicubic to avoid uneven pixel widths.
Encoder choice by GPU
- GeForce RTX 40 or 50 series: NVENC H.264 for Twitch at preset P6 with High Quality tuning; NVENC AV1 for YouTube.
- GeForce RTX 20 or 30 series: NVENC H.264 at P5 or P6 for Twitch; NVENC HEVC for YouTube.
- GTX 16 series: NVENC H.264 at P4 or P5, ideally at 900p or 720p.
- Radeon RX 7000 or 9000: AMD HW H.264 on the Quality preset for Twitch; AMD HW AV1 for YouTube. The RX 6000 series has no AV1 encoder, so use H.264 or HEVC.
- Intel Arc or 12th-gen and newer integrated graphics: QSV H.264 at TU4 (Balanced). If Minecraft and the encoder share the same integrated GPU, drop to 720p30.
- x264 on the CPU: Only with 8 or more cores, the veryfast preset and 720p. Minecraft loads and generates chunks on the CPU, so an x264 stream can stall exactly when you fly into new terrain.
Twitch Partners and Affiliates can tick Enable Enhanced Broadcasting under Settings, Stream to send a 1440p HEVC track at up to 9 Mbps alongside a 1080p H.264 track, which suits shader streams. Twitch doesn’t offer AV1 at the moment, so keep AV1 for YouTube, where 1080p60 in AV1 or HEVC has a recommended range of 4–12 Mbps.
In-game settings that keep OBS smooth
- Max Framerate: Cap it at your monitor’s refresh rate (or 120 for a 60 fps stream) instead of Unlimited. Menus and simple scenes can otherwise run at extreme frame rates that peg the GPU and starve OBS of render time.
- Render Distance: Load grows with the square of the distance. A setting of 12 covers up to 625 chunk columns, 16 covers up to 1,089, and 32 covers up to 4,225, almost four times the work of 16. Streaming at 12–16 keeps vistas wide without choking the CPU.
- Simulation Distance: 8–10 in singleplayer keeps farms working while limiting CPU load.
- Particles: Decreased cuts the noisy bursts from rain, explosions and potion effects that encode poorly.
- Shaders: With Iris and a shader pack, cap the game at 60–90 fps and turn off motion blur and film grain if your pack has them; both look worse after compression than they do on your monitor.
- Performance mods: Sodium (for Fabric or NeoForge) commonly raises Java frame rates, which you can then convert into GPU headroom with a lower cap.
- Memory: The vanilla launcher allocates 2 GB by default. Heavy modpacks often need 6–8 GB, but allocate what the pack recommends rather than everything you have: on a 16 GB PC, giving Minecraft 10 GB or more leaves little for OBS, a browser and Discord.
Privacy on SMP and multiplayer streams
- The F3 debug screen shows your exact coordinates. Turn on Reduced Debug Info in Chat Settings so a reflexive F3 press doesn’t reveal a base location on a shared server.
- Switch to a starting-soon or BRB scene while you edit server entries or use Direct Connect, since those screens show the server address.
- F1 hides the HUD for clean cinematic shots, and an OBS stream delay of 30–60 seconds (Settings, Advanced) protects hardcore or event streams from griefers watching live.
Audio setup
Use an Application Audio Capture source on javaw.exe or Minecraft.Windows.exe so game sound gets its own fader and track. Then use Minecraft’s Music and Sounds menu to lower the Music slider separately from effects; the soundtrack is quiet and atmospheric, but it can still mask your voice during long building sessions. Putting game audio on a separate recording track also lets you mute music in a VOD edit without losing your commentary.
Streaming Gear Worth Adding
Once OBS is tuned for Minecraft, audio and camera quality are what viewers notice next. These are common upgrades for a stream setup.
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
