Recording Your Witcher 3 Playthrough With a Facecam
You want to put yourself in the corner of your screen while showing off Witcher 3 gameplay. It sounds simple, but getting it to look clean without chewing up your GPU or making your streams unwatchable takes some actual effort. Most guides skip the part where your facecam looks washed out and tiny because you set it up wrong in OBS. I ran into this exact problem years ago when I first tried this format for a Witcher 3 series. The core setup involves layering a webcam feed over your game capture inside recording software. OBS Studio is the standard tool here. You add a game capture source for Witcher 3, then add a video capture device source for your camera, position it in a corner, and hit record. That is the basic mechanics. The reality is messier than that outline suggests. I spent about three hours tweaking resolution matching and bitrate settings before I got a recording that actually looked decent. The main issue I hit was my facecam appearing blurry and pixelated even though my webcam was capable of 1080p. The problem was that OBS was scaling a 1080p camera feed down to fit a small overlay area, and the software was using a low quality scaler by default. The workaround was switching the scaler to Bicubic sharpening in the video capture device properties, then setting the output resolution to match your display exactly rather than letting OBS auto-detect it. This alone cut my rendering artifacts nearly in half.
One thing nobody tells you about Witcher 3 specifically is that the game's built-in graphics settings can tank your recording quality if you are not careful. The "High Quality" post-processing filter in the graphics settings adds a bloom effect that looks great on monitor but absolutely destroys detail in recorded footage. It creates a hazy mess that makes your facecam look even worse since the contrast gets crushed. Switching that to Normal or off makes a visible difference in how sharp everything looks in playback. It also frees up some GPU headroom for encoding. Here is how I structured my actual OBS layout for this kind of content. The base canvas is set to 1920 by 1080 at 60 frames per second. The game capture source takes up the full background. My facecam sits in the bottom right corner at about 320 by 180 pixels with the green screen effect turned off and a thin black border added through the filter menu. I use the color correction filter on the camera feed to boost saturation slightly and raise the gamma by about five percent, which counters the dark lighting in Witcher 3's nighttime scenes. Without that adjustment, my face disappears into shadow during important moments. For encoding, use x264 if you have a decent CPU, or NVENC if you are on an NVIDIA card. The preset matters more than most people realize. Fast or P5 gives you a good balance between file size and visual quality without eating all your resources. Set the bitrate to somewhere between 6000 and 8000 kilobits per second for 1080p60. Going higher gives diminishing returns on a standard capture setup, and the files become unwieldy for editing later.
I also run Witcher 3 in exclusive fullscreen mode rather than borderless windowed. This reduces input latency and gives the game slightly better performance, but it does create one annoying quirk. If you alt tab out of the game while recording, OBS sometimes drops the game capture frame for a second or two when you return. It is a known issue with older versions of the game and certain GPU drivers. Updating to the latest version of Witcher 3 and keeping your graphics drivers current has mostly resolved this for me, but it still happens occasionally on my machine. The workaround is to pause the recording briefly before alt tabbing, then resume when you are back. Audio is another area where people mess up. Your microphone and game audio need to be on separate tracks if you plan to edit later. In OBS, go to Advanced Audio Properties and set your mic to Track 2 while keeping game audio on Track 1. This lets you mix them independently in post without any re-recording. I use this approach for all my Witcher 3 videos so I can adjust voice levels separately from the game soundtrack and dialogue. It takes maybe ten extra minutes in editing but saves hours of frustration. If you do not have a dedicated capture card and are doing everything through software capture, expect your CPU usage to spike during intense combat scenes. The Novigrad quests and the Blood and Wine expansions push the game hard enough that adding facecam encoding on top can cause frame drops in your recording even when the game itself runs fine. I noticed this during a Geralt versus multiple bandits encounter in Skellige where my recording stuttered despite a locked 60 frames per second on screen. Lowering the in-game shader quality and texture streaming settings helped stabilize the capture without changing the visual appearance too much in the final video.
Get the Full Details
There are trade offs to every part of this setup. A facecam overlay takes up screen space and can be distracting during dialogue heavy sequences. Some viewers find it annoying. It also requires you to actually set up and light your camera properly, which is an upfront investment of time and money. If you are just starting out and do not have a good webcam or lighting, consider recording gameplay first and adding a facecam later once you know the format works for your content. You can always composite it in after the fact with any basic video editor. The files also grow fast. A single two hour Witcher 3 playthrough at the settings I described produces roughly 5 to 7 gigabytes depending on scene complexity. Plan your storage accordingly and consider using a SSD for temporary recording if your main drive is slow. Encoding to a faster drive prevents dropped frames during the recording process itself, which is something I learned the hard way after losing an entire session to a write speed bottleneck. For editing, DaVinci Resolve has a free version that handles this kind of layered project well. Import both audio tracks separately, place the game footage on the main timeline, add your facecam as an overlay on a second track, and use keyframes to resize or reposition it if needed during cutscenes. It adds a bit more work compared to just hitting record and uploading, but the final product looks significantly more professional and gives you actual control over the viewing experience.
I record most of my Witcher 3 content using these parameters and the process has settled into something reliable. The initial setup took me probably six or seven hours across a weekend to get right, but now a fresh recording session takes about fifteen minutes from launch to finished file. The time you spend fine tuning the settings pays off every time after that.
