How to compress an exe with Crinkler?

Download Crinkler from the Releases page, then use it as a linker by replacing your standard linker in the build process. Refer to the manual.txt for specific command-line options and examples to minimize file size.

Crinkler vs UPX for small Windows executables?

Crinkler is optimized for demoscene intros and often achieves better compression ratios for executables under 8k, while UPX is more general-purpose and supports various platforms. For size-critical demos, Crinkler is the preferred choice among creators.

Can I use Crinkler for non-demoscene projects?

Yes, but it's best suited for small, native code executables where size is paramount. For larger applications or those with different priorities, general-purpose compressors or linkers might be more appropriate.

How to integrate Crinkler into a custom toolchain?

Use the Compressor library from the Crinkler project to estimate compressed sizes in your tools. Base your integration on the master branch to ensure version consistency, as recommended in the distribution section.

What size limits does Crinkler handle?

Crinkler is designed for executables of a few kilobytes, specifically targeting 1k, 4k, and 8k demoscene intros. It can compress slightly larger files but is most effective in this range.

Is Crinkler compatible with modern C++ compilers?

Yes, Crinkler works with output from compilers like MSVC or GCC for 32-bit Windows, but you'll need to link object files with Crinkler instead of the standard linker, as per the usage instructions.

Open-Awesome

Crinkler

NOASSERTIONC++v3.0a

A compressing linker for creating extremely small Windows demoscene executables (1k/4k/8k intros).

Visit Website GitHub

1.2k stars61 forks0 contributors

What is Crinkler?

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.

Target Audience

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.

Value Proposition

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.

Overview

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.

Use Cases

Best For

Creating 1k intros for Windows demoscene competitions
Building 4k or 8k demoscene productions with minimal executable size
Integrating executable compression into custom demoscene toolchains
Estimating compressed data size for size-optimized projects
Developing tools that require precise control over output file size
Producing tiny Windows executables for educational or experimental purposes

Not Ideal For

Developing 64-bit Windows applications or cross-platform software requiring broader compatibility
Projects where rapid development and ease of use are prioritized over achieving the smallest executable size
Teams using managed code environments like .NET or Java, as Crinkler is designed for native code compression
General software development needing features like debugging symbols or standard library linking

Pros & Cons

Pros

Extreme Size Optimization

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.

Demoscene Standard Tool

Widely adopted in the demoscene community, making it the go-to for competitions and productions where every byte counts, as noted in its philosophy.

Compressor Library Integration

Includes a separate compressor library that allows custom toolchains to estimate compressed data size, useful for development workflows, as described in the Building section.

Version Consistency

Embeds a version identifier in output files to match development branches, ensuring reliable builds when based on the master branch, per the distribution notes.

Cons

Platform and Architecture Limitations

Only produces 32-bit Windows executables, restricting use to specific environments and excluding modern 64-bit or cross-platform projects.

Complex Build Requirements

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.

Sparse Documentation and Support

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.

Frequently Asked Questions

Related Projects

ConfuserEx

An open-source, free protector for .NET applications

Stars2,863

Forks441

Last commit2 years ago

PEzor

Open-Source Shellcode & PE Packer

Stars2,107

Forks327

Last commit2 years ago

Amber

Reflective PE packer.

Stars1,417

Forks218

Last commit2 years ago

ProtectMyTooling

Multi-Packer wrapper letting us daisy-chain various packers, obfuscators and other Red Team oriented weaponry. Featured with artifacts watermarking, IOCs collection & PE Backdooring. You feed it with your implant, it does a lot of sneaky things and spits out obfuscated executable.

Stars1,079

Forks147

Last commit8 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

Crinkler

NOASSERTIONC++v3.0a

A compressing linker for creating extremely small Windows demoscene executables (1k/4k/8k intros).

Visit Website GitHub

1.2k stars61 forks0 contributors

What is Crinkler?

Target Audience

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.

Value Proposition

Overview

Use Cases

Best For

Creating 1k intros for Windows demoscene competitions
Building 4k or 8k demoscene productions with minimal executable size
Integrating executable compression into custom demoscene toolchains
Estimating compressed data size for size-optimized projects
Developing tools that require precise control over output file size
Producing tiny Windows executables for educational or experimental purposes

Not Ideal For

Developing 64-bit Windows applications or cross-platform software requiring broader compatibility
Projects where rapid development and ease of use are prioritized over achieving the smallest executable size
Teams using managed code environments like .NET or Java, as Crinkler is designed for native code compression
General software development needing features like debugging symbols or standard library linking

Pros & Cons

Pros

Extreme Size Optimization

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.

Demoscene Standard Tool

Widely adopted in the demoscene community, making it the go-to for competitions and productions where every byte counts, as noted in its philosophy.

Compressor Library Integration

Includes a separate compressor library that allows custom toolchains to estimate compressed data size, useful for development workflows, as described in the Building section.

Version Consistency

Embeds a version identifier in output files to match development branches, ensuring reliable builds when based on the master branch, per the distribution notes.