stb alternatives and similar libraries
Based on the "Miscellaneous" category.
Alternatively, view stb alternatives based on common mentions on social networks and blogs.
ZXing9.9 6.5 L3 stb VS ZXingZXing ("Zebra Crossing") barcode scanning library for Java, Android
C++ Format9.5 9.3 L1 stb VS C++ FormatA modern formatting library
HTTP Parser8.9 0.0 L1 stb VS HTTP Parserhttp request/response parser for c
RE28.9 6.5 L1 stb VS RE2RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
Cppcheck8.5 9.9 stb VS Cppcheckstatic analysis of C/C++ code
SDS8.0 0.0 L2 stb VS SDSSimple Dynamic Strings library for C
Klib8.0 0.0 L4 stb VS KlibA standalone and lightweight C library
ZBar7.8 0.0 L3 stb VS ZBarClone of the mercurial repository http://zbar.hg.sourceforge.net:8000/hgroot/zbar/zbar
American fuzzy lop7.6 0.0 stb VS American fuzzy lopamerican fuzzy lop - a security-oriented fuzzer
Serial Communication Library7.4 0.0 L1 stb VS Serial Communication LibraryCross-platform, Serial Port library written in C++
pdqsort6.6 0.0 stb VS pdqsortPattern-defeating quicksort.
PHP-CPP6.6 6.6 L4 stb VS PHP-CPPLibrary to build PHP extensions with C++
libssh26.4 5.8 stb VS libssh2the SSH library
Better Enums6.0 0.0 L5 stb VS Better EnumsC++ compile-time enum to string, iteration, in a single header file
c-smart-pointers5.8 0.0 stb VS c-smart-pointersSmart pointers for the (GNU) C programming language
Mach75.7 0.0 L2 stb VS Mach7Functional programming style pattern-matching library for C++
Experimental Boost.DI5.5 0.0 L3 stb VS Experimental Boost.DIDI: C++14 Dependency Injection Library
UNITS5.1 0.0 L3 stb VS UNITSa compile-time, header-only, dimensional analysis and unit conversion library built on c++14 with no dependencies.
stdman5.0 4.3 stb VS stdmanFormatted C++20 stdlib man pages (cppreference)
constexpr-8cc4.6 2.5 L3 stb VS constexpr-8ccCompile-time C Compiler implemented as C++14 constant expressions
SLRE4.5 0.0 L3 stb VS SLRESuper Light Regexp engine for C/C++
Stage4.3 0.0 L1 stb VS StageMobile robot simulator
outcome4.3 6.2 stb VS outcomeProvides very lightweight outcome<T> and result<T> (non-Boost edition)
cxx-prettyprint4.3 0.0 L5 stb VS cxx-prettyprintA header-only library for C++(0x) that allows automagic pretty-printing of any container.
DynaMix4.2 0.0 stb VS DynaMix:fish_cake: A new take on polymorphism in C++
libcpuid4.0 2.0 L2 stb VS libcpuida small C library for x86 CPU detection and feature extraction
STX3.9 9.5 stb VS STXC++17 & C++ 20 error-handling and utility extensions.
Better String3.9 0.0 L2 stb VS Better StringThe Better String Library
CppVerbalExpressions3.8 0.0 L5 stb VS CppVerbalExpressionsC++ regular expressions made easy
kangaru3.7 3.2 L5 stb VS kangaru🦘 A dependency injection container for C++11, C++14 and later
value-category-cheatsheet3.6 0.0 stb VS value-category-cheatsheetA C++14 cheat-sheet on lvalues, rvalues, xvalues, and more
leaf3.4 5.2 stb VS leafLightweight Error Augmentation Framework
casacore3.3 8.6 L1 stb VS casacoreSuite of C++ libraries for radio astronomy data processing
neither3.2 0.0 stb VS neitherEither and Maybe monads for better error-handling in C++ ↔️
libusb3.1 0.0 stb VS libusbAccess USB devices from Ruby via libusb-1.x
semver.c3.0 0.0 L5 stb VS semver.cSemantic version in ANSI C
gcc-poison3.0 0.0 stb VS gcc-poisongcc-poison
ub-canaries2.9 0.0 L4 stb VS ub-canariescollection of C/C++ programs that try to get compilers to exploit undefined behavior
StrTk2.9 0.0 stb VS StrTkC++ String Toolkit Library https://www.partow.net/programming/strtk/index.html
libnih2.7 0.0 L2 stb VS libnihNIH Utility Library
Boost.Signals2.6 3.2 L2 stb VS Boost.SignalsBoost.org signals2 module
sigslot2.4 0.0 L5 stb VS sigslotC++11 signal/slot implementation
QtVerbalExpressions2.4 0.0 L5 stb VS QtVerbalExpressionsThis Qt lib is based off of the C++ VerbalExpressions library. [MIT]
access_profiler2.2 0.0 L5 stb VS access_profilera tool to count accesses to member variables in c++ programs
FastFormat2.1 0.0 stb VS FastFormatThe fastest, most robust C++ formatting library
libsigc++2.1 0.7 L5 stb VS libsigc++A typesafe callback system for standard C++. [LGPL]
strf2.1 1.0 stb VS strfYet another C++ text formatting library.
cppq2.0 10.0 stb VS cppqSimple, reliable & efficient distributed task queue for C++17
libevil1.9 0.0 L4 stb VS libevilThe Evil License Manager
CommonPP1.9 0.0 L4 stb VS CommonPPSmall library helping you with basic stuff like getting metrics out of your code, thread naming, etc.
Write Clean C++ Code. Always.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of stb or a related project?
<!--- THIS FILE IS AUTOMATICALLY GENERATED, DO NOT CHANGE IT BY HAND --->
single-file public domain (or MIT licensed) libraries for C/C++
- image loader: [stb_image.h](stb_image.h)
- image writer: [stb_image_write.h](stb_image_write.h)
- image resizer: [stb_image_resize.h](stb_image_resize.h)
- font text rasterizer: [stb_truetype.h](stb_truetype.h)
- typesafe containers: [stb_ds.h](stb_ds.h)
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.
|[stb_vorbis.c](stb_vorbis.c)||1.22||audio||5584||decode ogg vorbis files from file/memory to float/16-bit signed output|
|[stb_hexwave.h](stb_hexwave.h)||0.5||audio||680||audio waveform synthesizer|
|[stb_image.h](stb_image.h)||2.27x||graphics||7901||image loading/decoding from file/memory: JPG, PNG, TGA, BMP, PSD, GIF, HDR, PIC|
|[stb_truetype.h](stb_truetype.h)||1.26||graphics||5084||parse, decode, and rasterize characters from truetype fonts|
|[stb_image_write.h](stb_image_write.h)||1.16||graphics||1724||image writing to disk: PNG, TGA, BMP|
|[stb_image_resize.h](stb_image_resize.h)||0.97||graphics||2634||resize images larger/smaller with good quality|
|[stb_rect_pack.h](stb_rect_pack.h)||1.01||graphics||623||simple 2D rectangle packer with decent quality|
|[stb_perlin.h](stb_perlin.h)||0.5||graphics||428||perlin's revised simplex noise w/ different seeds|
|[stb_ds.h](stb_ds.h)||0.67||utility||1897||typesafe dynamic array and hash tables for C, will compile in C++|
|[stb_sprintf.h](stb_sprintf.h)||1.10||utility||1906||fast sprintf, snprintf for C/C++|
|[stb_textedit.h](stb_textedit.h)||1.14||user interface||1429||guts of a text editor for games etc implementing them from scratch|
|[stb_voxel_render.h](stb_voxel_render.h)||0.89||3D graphics||3807||Minecraft-esque voxel rendering "engine" with many more features|
|[stb_dxt.h](stb_dxt.h)||1.12||3D graphics||719||Fabian "ryg" Giesen's real-time DXT compressor|
|[stb_easy_font.h](stb_easy_font.h)||1.1||3D graphics||305||quick-and-dirty easy-to-deploy bitmap font for printing frame rate, etc|
|[stb_tilemap_editor.h](stb_tilemap_editor.h)||0.42||game dev||4187||embeddable tilemap editor|
|[stb_herringbone_wa...](stb_herringbone_wang_tile.h)||0.7||game dev||1221||herringbone Wang tile map generator|
|[stb_c_lexer.h](stb_c_lexer.h)||0.12||parsing||940||simplify writing parsers for C-like languages|
|[stb_divide.h](stb_divide.h)||0.94||math||433||more useful 32-bit modulus e.g. "euclidean divide"|
|[stb_connected_comp...](stb_connected_components.h)||0.96||misc||1049||incrementally compute reachability on grids|
|[stb_leakcheck.h](stb_leakcheck.h)||0.6||misc||194||quick-and-dirty malloc/free leak-checking|
|[stb_include.h](stb_include.h)||0.02||misc||295||implement recursive #include support, particularly for GLSL|
Total libraries: 21 Total lines of C code: 43040
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
#define STB_IMAGE_IMPLEMENTATION #include "stb_image.h"
The right macro to define is pointed out right at the top of each of these libraries.
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 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?
Why public domain?
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
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.
*Note that all licence references and agreements mentioned in the stb README section above are relevant to that project's source code only.