What's Actually in My Video Editing PC (And What I'd Change)

Most “my editing PC” posts are written by someone who games on the side and edits a YouTube video once a month. This isn’t that. This build runs actual client work — client footage, real deadlines, exports that need to finish before I sleep. I priced every part myself after a full reformat, put it together, and I’ve been living on it since. There are at least three calls in this build I’d undo if I built it again tomorrow, and I’m not going to bury them at the bottom to make the post look cleaner. That’s usually where the useful part of a build post actually lives.

Disclosure: this post contains affiliate links. If you buy through them, I may earn a small commission — doesn’t change what you pay.

The Actual Parts List

Here’s everything in it, at what I paid in India:

CPU: AMD Ryzen 7 7800X3D, 8 cores / 16 threads — ₹40,569
Motherboard: MSI MAG B650 Tomahawk Wi-Fi — ₹23,753
GPU: ASRock Radeon RX 9060 XT Steel Legend OC, 16GB — ₹39,449
Monitor: BenQ GW2790Q, 27” 1440p IPS — ₹14,990
RAM: Crucial Pro 16GB DDR5-6000 — ₹13,500
SSD: WD_Black SN7100 500GB NVMe — ₹6,099
PSU: Ant Esports FG750 V2, 750W 80+ Gold — ₹4,900
Cooler: Zebronics AIO360 — ₹4,000
Case: Zebronics Zeb10 Zebargo — ₹3,750

Total: ₹1,51,010.

That’s the whole thing. Now let’s talk about whether it was money well spent, part by part.

The CPU: Right Chip, Wrong Reason Most People Would Pick It

The 7800X3D gets recommended constantly for content creators, and the reasoning behind that recommendation is usually a little off. It’s an 8-core, 16-thread Zen 4 chip with 96MB of 3D V-Cache — 104MB total once you count the L2 — running a 4.2GHz base and boosting to around 5.0GHz. It’s a 120W TDP part, and independent power testing has shown it often runs well under that in normal use, closer to 65–90W, because the V-Cache design keeps clocks and voltage conservative to protect the extra cache die.

That extra cache is a gaming feature first. It shaves latency off memory-heavy game engines, which is why every 7800X3D review leads with frame rates. For video editing, the win isn’t the cache — it’s that the chip is fast, efficient, and cheap to cool for its performance tier. Premiere Pro and DaVinci Resolve care more about sustained multi-threaded clock speed and how well the software’s media engine offloads to the GPU than they care about L3 cache size. If you’re choosing this chip specifically because you read “V-Cache helps editing,” you’re right about the outcome and wrong about the mechanism — which matters if you’re deciding between this and something like a Ryzen 9 with more cores for heavier multicam or 3D work.

For a single-user freelance editing rig doing 4K timelines, color work, and exports, eight cores at these clocks is genuinely enough. I haven’t hit a wall the CPU caused.

The GPU: A Genuinely Good Card for One Workflow, a Real Limitation for Another

The RX 9060 XT 16GB is RDNA 4, 32 compute units, 160W TDP, and — this is the part that matters — 16GB of VRAM at a price point where most competing cards from Nvidia top out at 8GB. For color grading and timeline playback, VRAM headroom is worth more than raw compute, and this card has more of it than cards costing meaningfully more.

Here’s the honest limitation, and it depends entirely on what software you cut in. DaVinci Resolve’s free version leans hard on GPU acceleration for color science, Fusion, and playback, and AMD cards run that acceleration fine through OpenCL. But Resolve Studio’s AI tools — Magic Mask, Smart Reframe, noise reduction — are built around Nvidia’s Tensor Cores, and they run noticeably faster on an RTX card than on anything AMD makes right now. Premiere Pro sits in the middle: it’s more CPU-forward for timeline playback, but its GPU-accelerated effects and Nvidia’s NVENC encoder still give Nvidia cards an edge on export speed that AMD’s AMF encoder doesn’t fully close.

So the real answer is: if you’re on free DaVinci Resolve or Premiere without heavy CUDA-dependent plugins, the 9060 XT’s extra VRAM is the smarter buy at this price. If you’re planning to eventually pay for Resolve Studio and lean on its AI tools, an equivalent Nvidia card would save you render time you’d otherwise be waiting on. I didn’t fully think through that tradeoff before buying — I bought for VRAM and general value, and it’s worked out, but it wasn’t a fully informed choice at the time.

The Motherboard: The One Part I Got Right Without Trying

The MSI B650 Tomahawk Wi-Fi has an 80A VRM setup, three M.2 slots, two PCIe 4.0 x16 slots, and support for DDR5 memory boosted well past 6400MHz. I’m using one of the three M.2 slots and none of the PCIe headroom. That’s not a complaint — it means whatever I do next (a second NVMe drive, a capture card, a future GPU swap) has a slot waiting for it without a motherboard upgrade. Wi-Fi 6E is a nice-to-have I didn’t need since the desk is wired, but it’s there.

If there’s a lesson in this part specifically, it’s that motherboard headroom is cheap insurance. Paying slightly more for expansion room you’re not using yet is a better trade than saving that money and hitting a wall in a year.

The RAM: My First Real Mistake

Sixteen gigabytes of DDR5-6000, and it’s a single stick. Not a 2x8GB kit — one 16GB module.

This is the mistake I’d fix first if I rebuilt today. Dual-channel memory roughly doubles effective bandwidth compared to a single stick at the same total capacity, and that bandwidth gets used constantly during editing: timeline scrubbing, effect previews, and how much footage the software can cache in RAM instead of re-reading from disk. Running single-channel on an editing rig is the kind of thing that doesn’t show up as a crash — it shows up as scrubbing that feels slightly laggier than it should, and you never quite trace it back to the RAM configuration unless you already know to look.

The fix isn’t complicated: 32GB across two sticks (even 2x16GB) would have cost more, but not dramatically more, and it solves two problems at once — dual channel and headroom for heavier timelines. Sixteen gigabytes total is also just thin for modern editing software with a browser and reference material open alongside it.

The Storage: My Second Real Mistake

The WD_Black SN7100 is a genuinely fast drive — up to 6800MB/s read, PCIe Gen 4, five-year warranty. Five hundred gigabytes of it is the problem.

A single 500GB drive has to hold your OS, every application, and your active project’s raw footage all at once. A couple hours of 4K footage from a mid-range camera can eat through a meaningful chunk of that on its own, before you’ve added project files, cache, and exports. What ends up happening in practice is constant shuffling — moving finished projects off to make room for the next one, or working straight off an external drive because the internal one’s full, which then becomes the actual bottleneck the fast NVMe speed was supposed to prevent.

If I rebuilt this, I’d either go with a 1TB or 2TB drive from the start, or keep the 500GB purely for OS and apps and add a second, larger drive for active project files. The second option is actually the better long-term habit — it means a Windows reinstall never touches your footage.

The Monitor, Cooler, PSU, and Case: The Parts Nobody Asks About

The BenQ GW2790Q is a solid 1440p IPS panel for the price, and it’s fine for general edit work. Worth being honest about, though: it’s a productivity monitor, not a grading display. It’s not calibrated for accurate color out of the box, and its color gamut coverage isn’t specced for the kind of color-critical work a dedicated grading monitor is built for. For cutting, titling, and general editing it’s genuinely good. For final color decisions on client-facing color grades, I’m trusting my eye and reference footage more than I’m trusting the panel, and that’s a limitation worth knowing before you buy one for the same reason I did.

The cooling and power side is where I probably overspent for what the build actually needs. A 360mm AIO on a chip that runs efficiently in the 65–90W range most of the time is more cooling than the workload demands — a good tower air cooler would have kept temperatures fine and freed up that budget for RAM or storage instead. Same logic applies to the 750W Gold PSU: this system’s real draw, CPU and GPU combined, sits well under 300W under load. 750W gives room for a future GPU upgrade, which isn’t a bad instinct, but if you’re not planning that upgrade soon, a 650W unit does the same job for less.

The case is a budget Zebronics chassis, and it does what a case needs to do — it holds everything and moves enough air that nothing throttles. It’s not going to win points on cable routing or dust filtration compared to pricier options, but for a desk that isn’t on display, it hasn’t been the limiting factor in anything I’ve done on this machine.

What I’d Actually Change If I Rebuilt This Today

In priority order: I’d go to 32GB of RAM across two sticks before anything else, because single-channel memory is the kind of mistake that quietly taxes every session rather than causing one dramatic failure. I’d size storage up to at least 1TB, ideally as a second dedicated drive rather than a bigger single one. And I’d actually sit down and figure out which NLE features I’m going to lean on before picking a GPU brand, instead of optimizing for VRAM-per-rupee and hoping the software side works out.

I would not change the CPU, the motherboard, or, honestly, the case. Those three did exactly what they needed to without asking for a second look.

If You’re Building One of These Yourself

The instinct with a budget editing build is to spend on the parts you can see — GPU, monitor, case lighting — and treat RAM and storage as an afterthought. My own build is proof of exactly how that goes wrong. Neither mistake broke anything. Both just made the machine slightly worse at its actual job than the spec sheet suggested it would be.

If you’re pricing out something similar, decide your storage and memory needs based on the footage you actually shoot, not the footage you’re editing in a demo video. Then spend what’s left on the GPU that matches the software you’re already committed to — not the one with the best specs-per-rupee on paper.

Building or upgrading an editing rig and want a second opinion before you buy? Get in touch and you’ll hear back within 24 hours.