Skip to content
stb single-file public domain libraries for C/C++
C C++
Branch: master
Clone or download
Latest commit f67165c Oct 29, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github pull request template Jan 16, 2017
data change map image formats to workaround stb_image bug Apr 16, 2016
deprecated deprecate rrsprintf Dec 5, 2016
docs other_libs points to new location Oct 8, 2016
tests more Travis fixing Aug 11, 2019
tools Update version numbers Aug 11, 2019
.travis.yml makefile Jan 16, 2017 Update Oct 28, 2019
stb.h Update version numbers Aug 11, 2019
stb_c_lexer.h Update version numbers Aug 11, 2019
stb_connected_components.h update version numbers Mar 4, 2019
stb_divide.h update version numbers Feb 25, 2019
stb_ds.h stb_ds: add documentation for STBDS_UNIT_TESTS, -std=c++0x Aug 12, 2019
stb_dxt.h Misc. comment typos Feb 12, 2018
stb_easy_font.h remove deprecated old-precision jpg path from stb_image.h Mar 3, 2017
stb_herringbone_wang_tile.h update version numbers Mar 4, 2019
stb_image.h Update version numbers Aug 11, 2019
stb_image_resize.h update version numbers Mar 4, 2019
stb_image_write.h Update version numbers Aug 11, 2019
stb_include.h add stb_include.h May 4, 2019
stb_leakcheck.h update version numbers Feb 7, 2019
stb_perlin.h stb_perlin: add non-power-of-two wrapping noise Aug 11, 2019
stb_rect_pack.h update version numbers Feb 25, 2019
stb_sprintf.h update version numbers Feb 7, 2019
stb_textedit.h stb_textedit: fix typo: STB_TEXTED_K_RIGHT May 4, 2019
stb_tilemap_editor.h update version numbers Mar 4, 2019
stb_truetype.h Update version numbers Aug 11, 2019
stb_vorbis.c stb_vorbis: fix typo in CVE number in docs Aug 11, 2019
stb_voxel_render.h update version numbers Mar 4, 2019
stretchy_buffer.h version numbers Jan 29, 2018


single-file public domain (or MIT licensed) libraries for C/C++


Most libraries by stb, except: stb_dxt by Fabian "ryg" Giesen, stb_image_resize by Jorge L. "VinoBS" Rodriguez, and stb_sprintf by Jeff Roberts.

library lastest version category LoC description
stb_vorbis.c 1.17 audio 5502 decode ogg vorbis files from file/memory to float/16-bit signed output
stb_image.h 2.23 graphics 7559 image loading/decoding from file/memory: JPG, PNG, TGA, BMP, PSD, GIF, HDR, PIC
stb_truetype.h 1.22 graphics 4888 parse, decode, and rasterize characters from truetype fonts
stb_image_write.h 1.13 graphics 1619 image writing to disk: PNG, TGA, BMP
stb_image_resize.h 0.96 graphics 2630 resize images larger/smaller with good quality
stb_rect_pack.h 1.00 graphics 628 simple 2D rectangle packer with decent quality
stb_ds.h 0.62 utility 1723 typesafe dynamic array and hash tables for C, will compile in C++
stb_sprintf.h 1.06 utility 1860 fast sprintf, snprintf for C/C++
stretchy_buffer.h 1.03 utility 262 typesafe dynamic array for C (i.e. approximation to vector<>), doesn't compile as C++
stb_textedit.h 1.13 user interface 1404 guts of a text editor for games etc implementing them from scratch
stb_voxel_render.h 0.88 3D graphics 3806 Minecraft-esque voxel rendering "engine" with many more features
stb_dxt.h 1.08b 3D graphics 728 Fabian "ryg" Giesen's real-time DXT compressor
stb_perlin.h 0.4 3D graphics 427 revised Perlin noise (3D input, 1D output)
stb_easy_font.h 1.0 3D graphics 303 quick-and-dirty easy-to-deploy bitmap font for printing frame rate, etc
stb_tilemap_editor.h 0.41 game dev 4161 embeddable tilemap editor
stb_herringbone_wa... 0.7 game dev 1221 herringbone Wang tile map generator
stb_c_lexer.h 0.11 parsing 966 simplify writing parsers for C-like languages
stb_divide.h 0.92 math 421 more useful 32-bit modulus e.g. "euclidean divide"
stb_connected_comp... 0.96 misc 1049 incrementally compute reachability on grids
stb.h 2.35 misc 14453 helper functions for C, mostly redundant in C++; basically author's personal stuff
stb_leakcheck.h 0.5 misc 190 quick-and-dirty malloc/free leak-checking
stb_include.h 0.01 misc 288 implement recursive #include support, particularly for GLSL

Total libraries: 22
Total lines of C code: 56088


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.

Are there other single-file public-domain/open source libraries with minimal dependencies out there?


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 and 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?

If people submit them, I generally add them, but the goal of stb_image is less for applications like image viewer apps (which need to support every type of image under the sun) and more for things like games which can choose what images to use, so I may decline to add them if they're too rare or if the size of implementation vs. apparent benefit is too low.

Do you have any advice on how to create my own single-file library?


Why public domain?

I prefer it over GPL, LGPL, BSD, zlib, etc. for many reasons. Some of them are listed here:

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.

You can’t perform that action at this time.