A compressing linker for creating extremely small Windows demoscene executables (1k/4k/8k intros).
Crinkler is a compressing linker for Windows that specializes in producing extremely small 32-bit executables, typically just a few kilobytes in size. It solves the problem of creating demoscene intros (like 1k, 4k, or 8k productions) where file size is a critical constraint, by compressing and linking code into the smallest possible output.
Demoscene developers and creators who need to build Windows intros with strict size limits (e.g., 1k, 4k, 8k), as well as toolchain developers integrating compression into custom workflows.
Developers choose Crinkler because it is the most widely used and optimized tool for compressing tiny demoscene executables, offering superior compression ratios and specialized features for size-constrained productions that general-purpose compressors cannot match.
Crinkler is an executable file compressor (or rather, a compressing linker) for compressing small 32-bit Windows demoscene executables. As of 2026, it is the most widely used tool for compressing 1k/4k/8k intros.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Specializes in compressing executables down to just a few kilobytes, essential for demoscene intros with strict 1k, 4k, or 8k size limits, as highlighted in the key features.
Widely adopted in the demoscene community, making it the go-to for competitions and productions where every byte counts, as noted in its philosophy.
Includes a separate compressor library that allows custom toolchains to estimate compressed data size, useful for development workflows, as described in the Building section.
Embeds a version identifier in output files to match development branches, ensuring reliable builds when based on the master branch, per the distribution notes.
Only produces 32-bit Windows executables, restricting use to specific environments and excluding modern 64-bit or cross-platform projects.
Requires Visual Studio 2022 or later and nasm.exe in the executable path, which can be a barrier for developers not using these specific tools.
Relies on a manual.txt file and external forums like Pouët.net for help, which may not offer immediate or comprehensive assistance for newcomers.