Crinkler

Crinkler is a free, open-source linker for producing compact 32-bit Windows executables, particularly demoscene intros in 1k, 4k and 8k sizes. It combines linking with compression, and the resulting executable decompresses into memory when run. By default, it uses context modelling and compresses code, optional text, and general data as separate parts. Crinkler can stand in for the Visual Studio linker and supports its basic options, configured through Visual Studio project settings. Its data compressor is also available as a separate library for tools that estimate compressed data size. Crinkler 3.0 requires Windows 10 or later and SSE4.2; programs it produces also require SSE4.2, though they may target older Windows versions. Each part is limited to 64k uncompressed. The manual cautions that tiny-header mode can make decompression prohibitively slow for files substantially larger than 1 KB. Downloads and a usage manual are available through the project’s GitHub pages. The software is distributed under the zlib license, which permits commercial use subject to its conditions.

Crinkler is tailored to small Windows demoscene executables, with Visual Studio linker support and a separate compressor library. Check its Windows and SSE4.2 requirements, per-part size limit, and tiny-header behavior before choosing it.

Crinkler suits demoscene creators making small 32-bit Windows intros, including 1k, 4k and 8k productions. It may also suit developers integrating a compressor or linker into a toolchain.

Crinkler is a specialized linker-compressor for creators of very small 32-bit Windows demoscene programs. It is best suited to 1k, 4k and 8k intro teams already comfortable with tight binary budgets and Windows build tooling. Its focused workflow is compelling for that niche, while hardware, format and input-size constraints make it unsuitable as a universal executable packer.

Overview

Crinkler combines linking and compression in one build step, creating an executable that decompresses itself into memory when launched. That design removes a separate post-link packaging stage and keeps size reduction central to the build, which is valuable when a production is measured in kilobytes rather than megabytes.

The project is free and open source under the zlib license. That license permits use, including commercial applications, subject to its conditions. The current release is Crinkler 3.0b, with downloads provided through the project's GitHub Releases page. A separate compressor library can help other tools estimate compressed data size, making Crinkler useful as a component in custom toolchains as well as a standalone linker.

Key features

Context-modelled compression

Crinkler uses context modelling and, by default, compresses code, optional text data and general data as separate parts. Separating those categories gives demoscene authors control over how a tiny output is assembled, but it also imposes a 64k uncompressed limit on each part in version 3.0. Inputs beyond that boundary need to be redesigned or handled by another tool.

Visual Studio linker replacement

Crinkler can replace the Visual Studio linker, supports its basic options and is configured through Visual Studio project settings. For Windows developers already using that environment, this is a more direct workflow than introducing an unrelated packer after compilation. Integrators can build Crinkler into other tools or toolchains; the project recommends basing integrations on the master branch.

Compact-output trade-offs

Tiny-header mode targets the smallest possible overhead, but decompression can become prohibitively slow when files are significantly larger than 1 KB. That mode therefore makes sense for genuinely tiny intros, not for ordinary Windows utilities where startup time matters more than the last bytes saved.

Pricing

Crinkler costs nothing, with no paid tiers, trial period or recurring renewal. The free plan is the complete compressing linker for small 32-bit Windows executables and is distributed under the zlib license. There are no seat or usage quotas stated, so the main commercial consideration is compliance with the license conditions rather than a subscription commitment.

Platforms

Crinkler runs on Windows and produces EXE files for 32-bit targets. Crinkler 3.0 requires Windows 10 or later, although generated executables can target older Windows versions. Both Crinkler 3.0 and the executable files it produces require a processor with SSE4.2 support, a significant compatibility check for older hardware.

Building the project requires Visual Studio 2022 or later. Custom assembly build rules also require nasm.exe on the executable path. These requirements matter mainly to developers compiling or integrating the tool; users downloading a release can obtain binaries from GitHub Releases.

Who it's for

Crinkler is the right choice for demoscene creators pursuing 1k, 4k or 8k Windows intros, especially those using Visual Studio and willing to tune code, text and data around strict per-part limits. It also suits tool authors who need a compressor library for size estimation or want to integrate a specialized linker into a Windows pipeline.

It is a poor fit for cross-platform projects, 64-bit executable workflows, general software distribution or binaries that cannot assume SSE4.2. Teams with inputs larger than 64k in any part, or with ordinary startup-time expectations, should look elsewhere.

Pros and cons

• Pro: Linking and compression are combined, reducing the need for a separate packaging stage in tiny-output builds.
• Pro: Visual Studio project-setting integration fits established Windows development workflows.
• Pro: The zlib license permits commercial use, and the tool is free and open source.
• Pro: A separate compressor library supports custom tools that need compressed-size estimates.
• Con: SSE4.2 is required by both the tool and produced executables, excluding older CPUs.
• Con: Each part is capped at 64k uncompressed, limiting projects beyond demoscene-scale inputs.
• Con: Tiny-header mode may decompress prohibitively slowly above roughly 1 KB.
• Con: Windows-only, 32-bit EXE output does not serve modern cross-platform or 64-bit applications.

Alternatives

Browse Executable Packers for a broader category view. Choose Obsidian instead if you need a freemium packer spanning Windows, macOS, Linux, Android, iOS and browser extensions, with a free plan billed without limits. StarForce Reader is a free, multi-platform option when document reading rather than demoscene executable compression is the requirement.

Virbox Protector is the alternative for buyers seeking paid protection software with a trial and native x86 personal or enterprise licenses. Windows PE Packer is another free Windows utility for processing 32-bit EXE files. papaw is free, unencumbered MIT-licensed software for Linux and self-hosted deployments.

AlushPacker, Enigma Virtual Box and MPRESS are free alternatives; MPRESS additionally supports PE32, PE32+, .NET and Mac-Darwin formats.

Verdict

Choose Crinkler when your goal is a tiny 32-bit Windows demoscene executable and every kilobyte counts. Its integrated linker, context-modelled compression, Visual Studio support and permissive licensing make it unusually well matched to that job. Look elsewhere for 64-bit or cross-platform output, inputs over its per-part ceiling, older CPUs without SSE4.2, or projects where decompression speed and general-purpose packaging matter more than extreme size reduction.