The stb repository is a collection of 21 single-file public domain libraries for C and C++ that provide functionality across graphics, audio, utilities, game development, and parsing. All libraries are released under dual licensing as either public domain or MIT, allowing developers to choose their preferred legal framework. The repository contains approximately 51,166 lines of C code distributed across these individual header files, each designed to be self-contained and easy to integrate into projects.
The most prominent libraries address image processing needs. stb_image.h handles image loading and decoding from multiple formats including JPG, PNG, TGA, BMP, PSD, GIF, HDR, and PIC. stb_image_write.h provides image writing capabilities for PNG, TGA, and BMP formats. stb_image_resize2.h offers image resizing with quality considerations. For font rendering, stb_truetype.h parses, decodes, and rasterizes characters from TrueType fonts. Additional graphics utilities include stb_rect_pack.h for 2D rectangle packing, stb_perlin.h for Perlin noise generation, stb_dxt.h for DXT compression, and stb_voxel_render.h for Minecraft-style voxel rendering.
Audio functionality is provided through stb_vorbis.c, which decodes Ogg Vorbis files to float or 16-bit signed output, and stb_hexwave.h, a waveform synthesizer. Utility libraries include stb_ds.h for typesafe dynamic arrays and hash tables in C, stb_sprintf.h for fast string formatting, and stb_textedit.h containing text editing functionality for games. Game development support extends to stb_tilemap_editor.h for embeddable tilemap editing and stb_herringbone_wang_tile.h for procedural tile map generation. Parsing utilities include stb_c_lexer.h for C-like language parsing, while stb_divide.h provides mathematical utilities and stb_connected_components.h handles grid reachability computation.
The single-file design philosophy addresses practical deployment challenges, particularly on Windows where standard library directories are absent. This approach eliminates the need for complex build systems or library management while avoiding runtime library conflicts. The README explicitly notes that security-relevant bugs are discussed publicly in GitHub Issues and Pull Requests, with implementation timelines that may be substantial, recommending careful consideration for security-sensitive projects. The repository also maintains a curated list of other single-file libraries at a separate GitHub repository for developers seeking alternative implementations.
