A look at nothings/stb: 35.0k stars on GitHub, written primarily in C. stb single-file public domain libraries for C/C++
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
single-file public domain (or MIT licensed) libraries for C/C++
Several projects have been moved to their own repositories:
image resize: stb_image_resize
sprintf: stb_sprintf
This project discusses security-relevant bugs in public in Github Issues and Pull Requests, and it may take significant time for security fixes to be implemented or merged. If this poses an unreasonable risk to your project, do not use stb libraries.
Noteworthy:
image loader: stb_image.h
image writer: stb_image_write.h
font text rasterizer: stb_truetype.h
typesafe C containers: stb_ds.h
Most libraries by stb, except: stb_dxt by Fabian "ryg" Giesen
library
latest version
category
LoC
description
last updated
stb_vorbis.c
1.24
audio
5704
decode ogg vorbis files from file/memory to float/16-bit signed output
parse, decode, and rasterize characters from truetype fonts
2026-11-12
stb_image_write.h
1.18
graphics
1924
image writing to disk: PNG, JPG, BMP, TGA, HDR
2026-11-12
stb_rect_pack.h
1.02
graphics
628
simple 2D rectangle packer with decent quality
2026-11-08
stb_perlin.h
0.6
graphics
517
perlin's revised simplex noise w/ different seeds
2026-11-08
stb_ds.h
0.98
utility
1942
typesafe dynamic array and hash tables for C, will compile in C++
2026-11-08
stb_textedit.h
1.16
user interface
1480
guts of a text editor for games etc implementing them from scratch
2026-11-12
stb_voxel_render.h
0.90
3D graphics
3808
Minecraft-esque voxel rendering "engine" with many more features
2026-11-08
stb_dxt.h
1.13
3D graphics
721
Fabian "ryg" Giesen's real-time DXT compressor
2026-11-08
stb_easy_font.h
1.2
3D graphics
306
quick-and-dirty easy-to-deploy bitmap font for printing frame rate, etc
2026-11-08
stb_tilemap_editor.h
0.43
game dev
4206
embeddable tilemap editor
2026-11-08
stb_herringbone_wa...
0.7
game dev
1232
herringbone Wang tile map generator
2026-11-01
stb_c_lexer.h
0.13
parsing
1068
simplify writing parsers for C-like languages
2026-11-11
stb_divide.h
1.0
math
310
more useful 32-bit modulus e.g. "euclidean divide"
2026-11-08
stb_connected_comp...
0.97
misc
1050
incrementally compute reachability on grids
2026-11-08
stb_leakcheck.h
0.7
misc
206
quick-and-dirty malloc/free leak-checking
2026-11-08
stb_include.h
0.3
misc
378
implement recursive #include support, particularly for GLSL
2026-11-08
Total libraries: 19
Total lines of C code: 39279
FAQ
What's the license?
These libraries are in the public domain. You can do anything you
want with them. You have no legal obligation
to do anything else, although I appreciate attribution.
They are also licensed under the MIT open source license, if you have lawyers
who are unhappy with public domain. Every source file includes an explicit
dual-license for you to choose from.
How do I use these libraries?
The idea behind single-header file libraries is that they're easy to distribute and deploy
because all the code is contained in a single file. By default, the .h files in here act as
their own header files, i.e. they declare the functions contained in the file but don't
actually result in any code getting compiled.
So in addition, you should select exactly one C/C++ source file that actually instantiates
the code, preferably a file you're not editing frequently. This file should define a
specific macro (this is documented per-library) to actually enable the function definitions.
For example, to use stb_image, you should have exactly one C/C++ file that doesn't
include stb_image.h regularly, but instead does
The right macro to define is pointed out right at the top of each of these libraries.
If I wrap an stb library in a new library, does the new library have to be public domain/MIT?
No, because it's public domain you can freely relicense it to whatever license your new
library wants to be.
What's the deal with SSE support in GCC-based compilers?
stb_image will either use SSE2 (if you compile with -msse2) or
will not use any SIMD at all, rather than trying to detect the
processor at runtime and handle it correctly. As I understand it,
the approved path in GCC for runtime-detection require
you to use multiple source files, one for each CPU configuration.
Because stb_image is a header-file library that compiles in only
one source file, there's no approved way to build both an
SSE-enabled and a non-SSE-enabled variation.
While we've tried to work around it, we've had multiple issues over
the years due to specific versions of gcc breaking what we're doing,
so we've given up on it. See https://github.com/nothings/stb/issues/280
and https://github.com/nothings/stb/issues/410 for examples.
Some of these libraries seem redundant to existing open source libraries. Are they better somehow?
Generally they're only better in that they're easier to integrate,
easier to use, and easier to release (single file; good API; no
attribution requirement). They may be less featureful, slower,
and/or use more memory. If you're already using an equivalent
library, there's probably no good reason to switch.
Can I link directly to the table of stb libraries?
You can use this URL to link directly to that list.
Why do you list "lines of code"? It's a terrible metric.
Just to give you some idea of the internal complexity of the library,
to help you manage your expectations, or to let you know what you're
getting into. While not all the libraries are written in the same
style, they're certainly similar styles, and so comparisons between
the libraries are probably still meaningful.
Note though that the lines do include both the implementation, the
part that corresponds to a header file, and the documentation.
Why single-file headers?
Windows doesn't have standard directories where libraries
live. That makes deploying libraries in Windows a lot more
painful than open source developers on Unix-derivates generally
realize. (It also makes library dependencies a lot worse in Windows.)
There's also a common problem in Windows where a library was built
against a different version of the runtime library, which causes
link conflicts and confusion. Shipping the libs as headers means
you normally just compile them straight into your project without
making libraries, thus sidestepping that problem.
Making them a single file makes it very easy to just
drop them into a project that needs them. (Of course you can
still put them in a proper shared library tree if you want.)
Why not two files, one a header and one an implementation?
The difference between 10 files and 9 files is not a big deal,
but the difference between 2 files and 1 file is a big deal.
You don't need to zip or tar the files up, you don't have to
remember to attach two files, etc.
Why "stb"? Is this something to do with Set-Top Boxes?
No, they are just the initials for my name, Sean T. Barrett.
This was not chosen out of egomania, but as a moderately sane
way of namespacing the filenames and source function names.
Will you add more image types to stb_image.h?
No. As stb_image use has grown, it has become more important
for us to focus on security of the codebase. Adding new image
formats increases the amount of code we need to secure, so it
is no longer worth adding new formats.
Do you have any advice on how to create my own single-file library?
I prefer it over GPL, LGPL, BSD, zlib, etc. for many reasons.
Some of them are listed here:
https://github.com/nothings/stb/blob/master/docs/why_public_domain.md
Why C?
Primarily, because I use C, not C++. But it does also make it easier
for other people to use them from other languages.
Why not C99? stdint.h, declare-anywhere, etc.
I still use MSVC 6 (1998) as my IDE because it has better human factors
for me than later versions of MSVC.
The most recent commit recorded on nothings/stb was 7 days ago, based on the GitHub push timestamp. The repository has 8.1k forks — one of the better signals of community interest.
How many stars does nothings/stb have?
nothings/stb has 35.0k GitHub stars — refresh the page for the live number, or check github.com/nothings/stb. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is nothings/stb open source?
TopGit's metadata for nothings/stb does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What is nothings/stb?
nothings/stb (nothings/stb) is a C project on GitHub. From the project's own README: stb single-file public domain libraries for C/C++
Where do I read more about nothings/stb?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/nothings/stb is the definitive source.
Read full README in the tab above.
Want a second opinion on stb?
Ask an AI that can read this page — one click and you get its take on stb.