Palworld Gameplay 4K 60fps With Facecam

How I Capture Palworld in 4K at 60fps With My Face Cam Running

The issue isn't actually that hard to pull off. It's mostly about knowing which settings fight each other and which ones you can safely ignore. I spent about three weeks debugging dropped frames before I landed on something stable. I use OBS Studio for capture. The free version works fine and there's no reason to pay for anything else at this point. Pair it with a NVENC encoder since you're likely running an NVIDIA card. If you're on AMD, use AMF or Video Encode. Intel Arc users should go with QSV. Pick the hardware encoder that matches your GPU.

Palworld Gameplay 4K 60fps With Facecam — The Settings That Actually Work

Here's my current preset. Base resolution is 3840 by 2160. Output scaled resolution stays the same unless you need to compress the file for upload. Frame rate is locked at 60. Keyframe interval sits at 2 seconds. Rate control is CBR if you're streaming, VBR if you're just recording locally. VBR gives you noticeably cleaner edges in fast motion without burning through disk space. Bitrate for 4K 60 is where most people mess up. I run 45 megabits per second for local recordings. That's enough for Palworld's texture-heavy environments and the blur effects during PVP combat. If you lower it past 35, you start seeing blockiness around Pals moving fast. If you're uploading to YouTube, cranking it to 60 or even 70 helps because YouTube re-encodes everything anyway. They compress your file down regardless, so you might as well give them more to work with. CPU usage should sit around 2 to 4 percent with NVENC. If it spikes above 8, you're either using the wrong preset or something else is eating your GPU. Check Task Manager before you start recording. Close whatever you don't need. Palworld itself will push your GPU hard, so leave breathing room.

The face cam portion runs at 1080p 30fps in a separate camera source inside OBS. I layer it over the bottom right corner at about 25 percent of the screen width. I used to run the camera at 60fps too, but it was pointless. Nobody watches their own face at 60fps while playing a game. It just doubles your encoding load for zero visible gain. 30fps is fine. 25fps would be fine too. Lower it if you're struggling for frames. One thing I learned the hard way: Palworld's own resolution scaling setting will wreck your frame capture if you leave it on auto. I noticed my recorded footage looked softer than my monitor output. Turns out the game was rendering internally at about 1.5K and upscaling to fill the screen. I disabled resolution scaling entirely and set it to 100 percent fixed. Suddenly my 4K capture matched what I was seeing on screen exactly. This fixed the blurry foliage and wall textures that always bothered me in post.

Audio Setup and Common Pitfalls

Record system audio and mic audio as separate tracks. Don't mix them into one stereo track inside OBS. When you edit later, having them separate means you can fix mic levels without touching game audio. It saves about twenty minutes per video on average. Watch out for the audio sync drift. It doesn't happen often, but I've seen it after recordings longer than forty minutes. I hit it once during a long Pal raid session. The video was ahead of the audio by roughly half a second. I fixed it in DaVinci Resolve by nudging the audio clip left until it matched. To prevent it, I enable the "synchronize to audio clock" option under Advanced in OBS settings now. Haven't had a drift issue since. Another practical note: if your framerate dips below 50 consistently during capture, drop the resolution scaling in Palworld to 90 percent first before touching any OBS settings. The game itself is the bottleneck, not your encoder. Dropping internal resolution inside the game costs way less in visual quality than lowering your OBS output resolution. People always do it backwards.

Storage and File Management

A forty-five minute 4K 60 recording at 45 Mbps comes out to roughly 120 gigabytes. Make sure your recording drive is an NVMe SSD. A regular SATA SSD will fill up its write cache and cause frame drops during long sessions. I use a dedicated 1TB NVMe just for recordings. Everything else lives on slower drives. Compress your files before uploading if you're not going straight to a stream. HandBrake with the H.265 medium preset cuts the file size to about a third while keeping the visual quality nearly identical. A 120GB file becomes roughly 40GB. Your upload time goes from overnight to about two hours on a decent connection. The whole setup takes about ten minutes to configure from scratch. After that, hitting record is just one click. The tradeoff is disk space and a GPU that's working fairly hard. If you're on a laptop or an older build, this workflow isn't going to look clean. Downgrade to 1440p and you'll see a massive difference in stability. Four thousand pixels at sixty frames is a lot for any system to handle consistently.