FREEDOM251

Freedom251 › Executable Packers

Crinkler

Free plan Windows

Visit Crinkler Alternatives Pricing

Crinkler's own site

What Crinkler is

Crinkler is a free, open-source compressing linker for making small 32-bit Windows executables, particularly demoscene productions such as 1k, 4k, and 8k intros. It combines linking and compression so the resulting executable decompresses into memory when run. By default, it uses context modelling and handles code, optional text data, and general data as separate parts. Crinkler can replace the Visual Studio linker and supports its basic options, with configuration available through Visual Studio project settings. Its data compressor is also available as a separate library for tools that need to estimate compressed data size. Crinkler is distributed under the zlib license, which permits use for any purpose, including commercial applications, subject to the license conditions. The project provides downloads through GitHub Releases and links to a manual for usage and version history. Crinkler 3.0 requires Windows 10 or later and SSE4.2, while executables it produces also require SSE4.2; it can target older Windows versions. The manual notes that tiny-header mode can make decompression prohibitively slow for files significantly larger than 1 KB.

Who it suits

Crinkler suits demoscene developers creating very small 32-bit Windows productions, including 1k, 4k, and 8k intros. It may also suit tool and toolchain makers who want to integrate its compressor or use its separate data-compression library.

What it does well

  • Combines linking and compression in one tool.
  • Supports Visual Studio linker replacement and basic options.
  • Separately available compressor library can estimate compressed data size.
  • Zlib license permits commercial use subject to its conditions.

What to know first

  • Crinkler 3.0 requires Windows 10 or later to run.
  • Crinkler 3.0 and its output executables require SSE4.2.
  • Uncompressed size is limited to 64k per part.
  • Tiny-header mode can slow decompression for files significantly over 1 KB.

Limits

Crinkler 3.0 limits uncompressed size to 64k per part. Its tiny-header mode can make decompression prohibitively slow for files significantly larger than 1 KB.

Plans

PlanBilled and limitsPrice
Crinklercompressing linker for small 32-bit Windows executables · distributed under the Zlib licenseFree

As github.com lists them, read 9 Oct 2026. The maker's own page has the final word.

Getting started

  1. Open the GitHub Releases page and download the latest version.
  2. Use the manual for usage guidance and version history.
  3. Configure Crinkler through Visual Studio project settings if replacing the Visual Studio linker.
  4. For a custom assembly build, have Visual Studio 2022 or later and nasm.exe on the executable path.

Crinkler is a free linker and compressor for tiny 32-bit Windows executables, especially demoscene intros. Its combination of build integration and small-output focus makes it a specialist tool; Windows 10 or later and SSE4.2 are required to use version 3.0.

Overview

Crinkler joins linking and compression in one step, producing an executable that decompresses into memory when run. That workflow suits creators working to the tight size budgets of 1k, 4k and 8k productions better than developers seeking a general-purpose executable packer.

The current release is Crinkler 3.0b. It is open source under the zlib license, which permits commercial use subject to its conditions. Its compressor is also available as a separate library, which can help other tools estimate compressed data size.

Key features

Compression designed for small outputs

Crinkler uses context modelling and by default compresses code, optional text data and general data as separate parts. This gives makers a focused way to shrink a small production as part of its build. The trade-off is a 64k uncompressed limit for each part, which rules out inputs that exceed that boundary.

Visual Studio linker replacement

Crinkler can replace the Visual Studio linker, supports its basic options and is configured through project settings. That makes it a practical fit for Windows developers already using Visual Studio, though its integration does not change the tool’s narrow focus on 32-bit outputs.

Toolchain integration

The project welcomes integrations with other tools and toolchains and recommends using the master branch as their basis. That is useful for toolmakers who want to incorporate Crinkler’s compression workflow, while teams building Crinkler itself need Visual Studio 2022 or later; custom assembly build rules also require nasm.exe on the executable path.

Small-file caveat

Tiny-header mode can make decompression prohibitively slow for files significantly larger than 1 KB. It is therefore not a setting to assume is suitable across a project’s full size range.

Pricing

Crinkler is free: its Crinkler plan costs nothing and includes the compressing linker for small 32-bit Windows executables under the Zlib license. The perpetual license model and permission for commercial use make it available without a paid tier, though use remains subject to the license conditions. There is no free trial because the software is free.

Platforms

Crinkler runs on Windows, and version 3.0 requires Windows 10 or later. It produces EXE files for 32-bit architecture; both Crinkler 3.0 and the executables it creates require SSE4.2. Older Windows versions can be targeted, but the operating system and CPU requirements still constrain who can build and run it.

Who it's for

Crinkler is best suited to demoscene creators making small 32-bit Windows productions, particularly 1k, 4k and 8k intros. Visual Studio users get a route to combine linking and compression within project settings, while toolmakers may find the separate compressor library useful for estimating data size.

It is a poor fit for projects with any part exceeding 64k uncompressed, users without SSE4.2, or developers who need a packer for architectures beyond 32-bit. General questions and discussion go to the Pouët.net forum; usage guidance and version history are covered in the manual.

Pros and cons

Pros

  • Combines linking and compression, avoiding a separate compression step for its intended small-executable workflow.
  • Visual Studio linker replacement and project-settings configuration suit developers already building in that environment.
  • Free, open-source distribution under a license that permits commercial use subject to its conditions.
  • A separate compressor library can help toolmakers estimate compressed data size.

Cons

  • Windows 10 or later and SSE4.2 limit compatibility for version 3.0 and its output executables.
  • The 64k uncompressed ceiling per part excludes larger inputs.
  • Tiny-header mode can make decompression prohibitively slow on files significantly larger than 1 KB.
  • Its 32-bit Windows focus makes it unsuitable for other target architectures.

Alternatives

For a broader set of executable-packing options, browse Executable Packers.

  • Obsidian is worth considering if cross-platform availability matters: it supports Android, iOS, Linux, macOS, Windows and extensions, and has a free plan without limits or sign-up.
  • StarForce Reader is a free alternative available across Android, iOS, Linux, macOS and Windows.
  • UPX is a free option for users seeking an executable packer on Linux, macOS or Windows.
  • MPRESS is another free option, available for macOS and Windows, with PE32, PE32+, .NET and MAC-DARWIN formats.
  • papaw may suit users looking for free software on Linux or a self-hosted setup.
  • Windows PE Packer is a free Windows alternative that processes 32-bit .exe files.
  • AlushPacker is a free Windows alternative.
  • Enigma Virtual Box is a free Windows application-virtualization option.

Verdict

Choose Crinkler if you are building tiny 32-bit Windows demoscene executables and want linking and compression combined in your workflow. Its focused compression and Visual Studio support are strong fits for that job, but the Windows 10 and SSE4.2 requirements, 32-bit target and 64k-per-part limit make another tool the better choice for broader compatibility or larger inputs.

Verdict

Choose Crinkler if you are building small 32-bit Windows demoscene executables and want linking and compression in one step. Look elsewhere if your environment cannot meet its Windows and SSE4.2 requirements, or if your files exceed its per-part size limit.

Questions

How much does Crinkler cost?

The listed Crinkler plan is free. It is open source and distributed under the zlib license.

Which operating systems does it support?

Crinkler is for Windows. Version 3.0 requires Windows 10 or later, though it can target older Windows versions.

What architecture does it support?

Crinkler is described as a compressing linker for small 32-bit Windows executables.

Can I use Crinkler with Visual Studio?

It can replace the Visual Studio linker, supports its basic options, and can be configured through project settings.

Where can I download it and get support?

The README directs users to GitHub Releases for downloads and to the Pouët.net forum for general discussion, questions, and comments.

Facts from Crinkler's own pages

Audience
The project describes Crinkler as widely used for compressing 1k, 4k, and 8k intros. · github.com, 9 Oct 2026
Build requirements
Building requires Visual Studio 2022 or later, and nasm.exe on the executable path for custom assembly build rules. · github.com, 9 Oct 2026
Community support
The README directs general discussion, questions, and comments to the Pouët.net forum. · github.com, 9 Oct 2026
Compression method
The manual says Crinkler uses context modelling and compresses code, optional text data and general data as separate parts by default. · github.com, 8 Oct 2026
Compressor library
Its data compressor is available as a separate library that can help tools estimate compressed data size. · github.com, 9 Oct 2026
CPU requirement
Crinkler 3.0 and the executable files it produces require SSE4.2. · github.com, 9 Oct 2026
Current release
The Releases page lists Crinkler 3.0b as the latest release. · github.com, 9 Oct 2026
Documentation
The project links to a manual for usage information and version history. · github.com, 9 Oct 2026
Download
The README directs users to the GitHub Releases page for the latest version. · github.com, 9 Oct 2026
Downloads
The README directs users to the GitHub Releases page to download the latest version. · github.com, 8 Oct 2026
How it works
Crinkler combines linking and compression, producing an executable that decompresses into memory when run. · github.com, 8 Oct 2026
Input size limit
Crinkler 3.0 limits uncompressed size to 64k per part. · github.com, 9 Oct 2026
Integration
The project welcomes integrating Crinkler into other tools or toolchains and recommends using the master branch. · github.com, 9 Oct 2026
License
Crinkler is distributed under the Zlib license. · github.com, 9 Oct 2026
Notable limit
The manual says the tiny-header mode can make decompression prohibitively slow for files significantly larger than 1 KB. · github.com, 8 Oct 2026
OS requirement
Crinkler 3.0 requires Windows 10 or later, though it can target older Windows versions. · github.com, 9 Oct 2026
Purpose
Crinkler is a compressing linker for Windows executables that are only a few kilobytes in size, mainly for small demoscene productions. · github.com, 9 Oct 2026
Support
The README directs users to the Pouët.net forum for general discussion, questions and comments. · github.com, 8 Oct 2026
Target audience
The project describes Crinkler as a tool for compressing small 32-bit Windows demoscene executables, including 1k, 4k and 8k intros. · github.com, 8 Oct 2026
Visual Studio
Crinkler can replace the Visual Studio linker and supports its basic options, with configuration through Visual Studio’s project settings. · github.com, 8 Oct 2026

Where Crinkler stands on Freedom251

Look at these too