If you've been researching QBCore, you've probably run into QBox — a framework that started as a fork of QBCore and has built its own following. Understanding the difference helps you choose. Here's an honest comparison.
What QBox is
QBox began as a community fork of QBCore, created to address things some developers wanted improved — cleaner code, better performance in places, tighter integration with the modern ox stack, and a different development direction. It's not a totally separate universe; it shares DNA with QBCore, so much will feel familiar.
Why QBox exists
Forks happen when part of a community wants a different direction. QBox emerged from developers who wanted:
- Tighter ox integration — built around ox_lib, ox_inventory, and ox_target more natively
- Code cleanups and modernization in areas
- A particular development philosophy and pace
If you value the modern ox ecosystem and cleaner structure, QBox aims squarely at that.
The key differences
Ox-native design. QBox leans harder into the ox stack as a foundation, whereas QBCore has historically been more flexible about inventory/target choices. If you're all-in on ox, QBox feels natural.
Code style and structure. QBox has reworked parts of the codebase. Developers who've worked with both often describe QBox as cleaner in places.
Ecosystem size. This is the big practical one. QBCore has been around longer and has a larger library of scripts, tutorials, and community knowledge. QBox's ecosystem is growing but smaller. More scripts explicitly target QBCore.
Compatibility. Because QBox shares QBCore roots, many QBCore scripts work or can be adapted, but not all — and "works with QBCore" doesn't guarantee "works with QBox." Always check.
Which should you choose?
Choose QBCore if:
- You want the largest ecosystem and most available scripts
- You value extensive community knowledge and tutorials
- You want the most broadly-compatible option
Choose QBox if:
- You're building around the ox stack natively
- You prefer its cleaner structure and development direction
- You're comfortable with a smaller (but growing) ecosystem
For most newcomers, QBCore's larger ecosystem makes it the safer default. For developers who specifically want ox-native design and don't mind a smaller library, QBox is a strong modern choice. Neither is "wrong."
The compatibility question when buying scripts
Whichever you pick, check that scripts you buy support it. Some are QBCore-specific, some support both, some are QBox-specific. A script that supports multiple frameworks gives you flexibility if you ever switch.
At Viper Development, our scripts are built for broad compatibility across the QBCore/ESX ecosystem and the modern ox stack, so they slot into standard setups cleanly. Always check a script's stated framework support before buying — ours is clearly listed. Browse our scripts →.
Related reading
If you're still deciding on a framework at all, our QBCore vs ESX guide covers the bigger picture, and what is QBCore explains the foundation both share.