Why I built IDXDIAG

I built idxdiag because I love games. For years I ran into the same problem. I would find a game I wanted to play, then have no clear way to know if my PC, my laptop, or my Mac could actually run it. So I did what everyone does. I opened Windows Run, typed dxdiag, read my system details, then searched the game's requirements and tried to compare them in my head, line by line. RAM here, GPU there, VRAM somewhere else. It was slow, and it was easy to get wrong.

So I made the tool I always wanted. You upload your dxdiag file, or on Mac your system profile, and idxdiag reads your real hardware. Then you pick a game, and it compares your actual system against that game's minimum and recommended requirements. If you can run it, it tells you. If you cannot, it tells you exactly where you fall short, whether it is RAM, VRAM, GPU, or storage, so you know what to upgrade instead of guessing.

idxdiag does the same for three things, not just games. Games, so you know what you can play. Software, so you know what your machine can handle before you install it. And AI models, the local LLMs so many people now want to run at home. That last one barely exists anywhere else. Almost no site tells you whether your system can actually run a given model, or how much VRAM it really needs. idxdiag does, and it compares it against your real hardware the same way it does for games.

I built this because I wanted an honest, fast answer to one simple question, can my system run this. Now anyone can get it in about four seconds.