49,000 Stars and Still Climbing: The C++ JSON Library Everyone Uses

Why nlohmann/json became the default answer to a question C++ developers have asked for decades. Open any moderately serious C++ project on GitHub right now — a game engine, an embedded IoT firmware, a trading system — and there is a reasonable chance you will find a single line near the top: #include <nlohmann/json.hpp>. One file. No build system gymnastics. Just JSON that works. Setting C++ is a language that can do almost anything, but "almost anything" has historically excluded "parse JSON without wanting to quit programming." The language has no native JSON support, and for years the ecosystem offered a fragmented mess of competing libraries, each with different APIs, different pitfalls, and different opinions about how memory should be managed. Niels Lohmann, a software engineer in Germany, started solving his own problem somewhere around 2013. His goal was simple to state and hard to execute: a JSON library that felt like it belonged in modern C++ — one that used the language's own idioms rather than fighting them. The result is nlohmann/json, now sitting at nearly 50,000 GitHub stars with commits still landing as recently as April 2026. The number alone does not tell the whole story. The customers page in the repo's documentation shows logos from companies spanning automotive, aerospace, gaming, and enterprise software. This is not a weekend toy. It is infrastructure. The Story The library is header-only (meaning you drop one .hpp file into your project and you are done — no separate compilation step, no linking against a binary). That single design decision removed the biggest practical barrier to adoption in C++. Here is what everyday use looks like. Imagine you are building a configuration loader for a desktop application. Your config file arrives as a JSON string. With nlohmann/json, reading a nested value looks like this: auto config = nlohmann::json::parse(raw_string); std::string theme = config["ui"]["theme"]; int timeout = config["network"]["timeout_ms"]; No manual pointer casting. No "did I free that?" anxiety. The library maps JSON objects to C++ containers using the same bracket syntax you already know. Going the other direction — serializing a C++ struct back into JSON — requires adding a single macro or a small to_json / from_json function pair, and then nlohmann::json j = my_object; just works. Beyond basic JSON, the library supports CBOR and BSON (binary formats that are faster to transmit than text JSON), JSON Patch (a standard way to describe changes to a JSON document, useful for versioned configs or API diffs), and JSON Merge Patch (a simpler variant of the same idea). These are not bolt-ons. They share the same interface as everything else in the library. The documentation site at https://json.nlohmann.me is unusually good for a C++ open-source project. It is searchable, example-dense, and does not assume you already know the answer. The Insight What separates a library that reaches 50,000 stars from one that stalls at 500 is rarely the algorithm. It is the decision about what the user should not have to think about. nlohmann/json made one opinionated call: the API should feel like the JSON itself. Arrays behave like std::vector. Objects behave like std::map. If you know modern C++, you already know most of this library. That frictionless on-ramp is why it keeps spreading — not because someone ran a marketing campaign, but because every developer who uses it once recommends it the next time someone asks. The momentum right now is tied to two converging trends. C++ is experiencing a quiet renaissance in performance-critical domains: embedded AI inference, real-time systems, game engines that need to communicate with web APIs. All of those systems need to speak JSON. And as those projects proliferate on GitHub, new developers encounter nlohmann/json in existing codebases and carry it into their next project. The 49,000 stars are not a peak — they are a compounding curve. If you write any C++ that touches configuration files, REST APIs, or data serialization, this library is already the industry default in all but name. The question is not whether to evaluate it. The question is whether you want to be the person who still hasn't. The repo's activity log shows it is actively maintained, with contributors and issue responses staying current into 2026. That is a meaningful signal in a language ecosystem where abandonment is common. Start with the getting-started section at the documentation site, drop the header into your next project, and see how quickly the JSON problem disappears from your list. More rising projects like this one are tracked weekly at teum.io/stories. 한국어 요약 C++에서 JSON을 쉽게 다루기 위한 라이브러리로, 파일 하나만 프로젝트에 넣으면 바로 사용할 수 있는 헤더 전용 방식이 핵심입니다. 거의 5만 개에 달하는 GitHub 스타를 보유하며 지금도 활발히 유지보수되고 있고, 자동차·게임·항공우주 등 다양한 산업 현장에서 실제로 쓰이고 있습니다. 임베디드 AI, 실시간 시스템, 게임 엔진처럼 C++가 다시 주목받는 분야가 늘어나면서 이 라이브러리의 확산 속도도 함께 빨라지고 있습니다. C++ 프로젝트에서 JSON이 필요하다면, 사실상 업계 표준이 된 이 라이브러리를 먼저 확인해보세요. The question is not whether to evaluate it. The question is whether you want to be the person who still hasn't.