Chip synths, trackers, bitcrushers and resynthesisers. They are not competing products - they are four different jobs, and picking the wrong one is why most chiptune attempts sound like a broken MP3.
"Chiptune plugin" is a category that hides four completely different tools inside it. Before you pick one, you need to know whether you want to write chip music from scratch, convert audio you already recorded, or just rough up a sound you like. This guide sorts them by that question first, then lists the tools.
The sound of late-80s handheld and console music was a hardware budget, not a style choice. A typical sound chip gave a composer about four voices: two pulse waves with a few duty cycles, one small wavetable or triangle voice, and one noise generator. Tuning stepped in coarse increments because pitch lived in a small register. Everything you remember was written inside those walls.
So the test for any chiptune tool is simple - does it actually reproduce the constraints, or does it just add dirt?
Trackers are the original workflow: a pattern editor where you type notes and effect commands into columns, targeting a specific chip. Maximum authenticity, and still the best way to write chip music from nothing. The catch is that they are standalone applications with a learning curve that has nothing to do with how your DAW works.
Chip synth plugins put chip voices in your DAW as an instrument you play from MIDI. You keep your piano roll and your session; you give up some of the exact hardware quirks a dedicated tracker exposes. This is the right default for most producers writing chip parts.
Resynthesisers go the other direction. Instead of you playing a chip, they listen to audio you already have - a vocal, a bass, a hook - track its pitch and envelope, and replay that performance on modelled chip channels. This is the only approach that turns your own take into a chip line.
Bitcrushers and decimators do not synthesise anything. They reduce bit depth and sample rate on whatever passes through, which gets you grit, aliasing and lo-fi texture. Essential for drums and full mixes, where nothing can pitch-track. But a crushed vocal is a crushed vocal - it is not a chip playing your melody. If you only take one thing from this page, take that distinction.
A chiptune resynthesiser. It pitch-tracks incoming audio and rebuilds the performance on four modelled handheld-console sound-chip channels: two pulse channels with four duty cycles, a 32-sample 4-bit wavetable, and LFSR noise keyed off transients. Three independent cartridges - CHIP for the resynth, ARP for a host-synced arpeggiator (1/4 to 1/32, modes UP / DOWN / UPDN / RAND / CHRD, four octaves, 400 ms glide), and CRUSH ROM for decimation (1-16 bit, rate divide 1-64 with jitter, post filter down to 540 Hz). There are no knobs: you drive it with a D-pad and a four-shade dot-matrix screen. Eject all three cartridges and it is true passthrough that nulls against dry.
The limitation, stated plainly: tracking is monophonic. It needs one clear pitch at a time - a vocal, a bass, a lead. Chords and full mixes will not track, and no amount of tweaking changes that. For those, run CRUSH ROM on its own.
Best for: Turning a take you already recorded into a chip line. macOS VST3 / AU / AAX universal, Windows VST3 64-bit, 3 machines, no iLok, no subscription.
A free synth instrument you play from MIDI, built to sound like a classic 8-bit home console sound chip - pulse voices with selectable duty, a triangle-style voice, and noise, with the coarse envelope behaviour of the era. It has been a first stop for producers wanting chip parts in a DAW for years, and it is still the fastest way to find out whether you enjoy writing chip music at all before spending anything.
Best for: Writing chip melodies and basslines from MIDI in your existing session, for free.
A free, open-source, actively developed chiptune tracker that targets a wide range of vintage sound chips rather than just one. If your goal is music that a real chip could have played - correct channel counts, correct limitations, correct effect commands - a tracker is the honest route, and this is the modern one. Expect to learn a pattern editor: it does not work like a piano roll and it is not trying to.
Best for: Writing genuinely authentic multi-chip music from scratch, if you are willing to learn a tracker.
The long-standing free Windows tracker aimed at the classic 8-bit home console sound chip. An enormous amount of the chiptune scene's output was written in it, which means the tutorials, example modules and community knowledge around it are deep. Several community forks exist that extend the original. It is old software with an old interface, and that is exactly why the results sound period-correct.
Best for: Learning the classic console chip idiom from a huge back catalogue of community material.
A free, straightforward bit-depth and sample-rate reduction plugin. It does one job and does not pretend otherwise - which makes it a good honest test of the point above. Put it on a vocal and you get a degraded vocal; put it on a drum loop and you get chip-adjacent drums, which is genuinely useful because drums are exactly where resynthesis cannot help you. Every chiptune session needs a crusher somewhere; it does not need to be an expensive one.
Best for: Drums, loops and full mixes, where there is no single pitch to track.
Not a plugin at all - a commercial tracker that runs on the original handheld console hardware, or on an emulator if you do not have the hardware. It is the tool behind a large share of live chip performance, because the sound is not a model of the chip, it is the chip. Included here because any honest list of chiptune tools that omits it is incomplete, and because it explains what everything else in the category is approximating.
Best for: Purists, live performers, and anyone who wants the actual hardware in the signal path.
Plogue's work is the deep end of chip emulation: chipsounds covers a broad set of specific vintage sound chips in one instrument, and the company's chipsynth line goes further into individual systems. If you care about the difference between one manufacturer's chip and another's - not "8-bit" as an aesthetic but a particular piece of silicon - this is the level of detail you are looking for, and it is a paid product for good reason.
Best for: Producers who want a specific chip, historically modelled, rather than a generic 8-bit sound.
A paid bit and sample-rate reducer modelled on the converters in vintage samplers, rather than on plain digital truncation. That is a different flavour of lo-fi from a straight crusher - closer to early sampler grit than to chip hardware - and it is included here because a lot of what people call "chiptune drums" is really that sampler sound. Worth knowing which one you actually want before you buy either.
Best for: Sampler-flavoured lo-fi on drums and buses, if free crushers are not giving you the character you want.
This is not a quality ladder. The numbering groups the list by approach and by cost - our own tool, then the free options, then the paid ones - because a free tracker and a paid chip emulation are not competing for the same slot in your workflow.
Everything above assumes you are writing chip music. If instead you have a take you already love - a vocal hook, a bass line, a lead - and you want that performance playing on a chip, none of the trackers or MIDI synths will do it. That is the resynthesis job. Here is the method, using TALLBOY because it is the tool we built for exactly this.
A lead vocal or vocal double, a bass line, a single-note hook, a mono synth part. Pitch tracking needs one fundamental to lock onto - chords, pads and full mixes make any tracker chase partials and warble. That is physics, not a bug. Tighten the take first if it is messy; the chip voice follows what you feed it.
The resynth stage tracks pitch and envelope and replays them on the two pulse channels, the 32-sample 4-bit wavetable and the noise generator. The duty cycle is your main tone control: thin duties give you a nasal retro lead, wide duties sit closer to square-wave bass. Noise is keyed off transients, so consonants in a vocal turn into chip percussion on their own.
This is the step that separates "8-bit-ish" from chiptune. Sync the arp to the project - 1/16 UP across two octaves is the classic move - or use CHRD mode to fake harmony from a single monophonic line, which is exactly what chip composers did when they had no spare channel. Glide up to 400 ms turns a stepped arp into a slide instead.
CRUSH ROM last: modest bit reduction for sheen, hard rate divide with jitter and the post filter pulled down for full cartridge dirt. Then decide what the part is. Fully wet, it is a new instrument playing your melody. Blended 20-40% under the original, it is an 8-bit double that makes a hook feel twice as wide. For drums, eject CHIP and ARP and run CRUSH ROM alone - that is the honest way to get chip-adjacent percussion.
It depends what you are doing. To write chip parts from MIDI, a free chip-style synth instrument is the fastest route. For maximum authenticity, a free open-source tracker gets you closest to real hardware, at the cost of learning a pattern editor. If you only want crunch and texture on audio you already have, a free bitcrusher is enough. There is no single answer because these are not the same job.
No. Trackers are the authentic route and still the best tools for writing chip music from scratch, but they are standalone applications with their own workflow. If you already work in a DAW, a chip synth plugin or a resynthesiser fits your session without changing how you write.
No. A bitcrusher reduces bit depth and sample rate, degrading the audio you already have. That is lo-fi grit, not the sound of a chip playing your melody. Chiptune character comes from pulse waves, a small wavetable, hardware noise and stepped tuning - which needs synthesis or resynthesis, not degradation. Bitcrusher vs decimator covers the difference in detail.
Yes - that is what a resynthesiser is for. It pitch-tracks a monophonic source and replays the performance on modelled chip channels, so your own take drives the chip voice. It needs one clear pitch at a time, so vocals, bass lines and single-note leads work; chords and full mixes do not. See the 8-bit vocal effect guide for the vocal version specifically.
The plugins here load in any host that takes standard plugin formats. The trackers do not - they are standalone applications, and you bounce audio out of them and import it. That difference matters more than any feature list when you are choosing, so decide up front whether you want something inside your session or beside it.
Pick by job, not by price. If you want to write chip music from nothing, a free tracker or a free chip synth will take you further than anything you can buy, and one of them costs nothing to find out. If you want a specific historic chip modelled in detail, that is what the paid emulation instruments are for. If you only need texture on drums and mixes, a free crusher is enough and always was.
The one job none of those do is turning audio you already recorded into a chip performance. That needs pitch-tracked resynthesis with real channel modelling - pulse duties, a small wavetable, hardware noise, an arp. TALLBOY does that for $20 one-time, no subscription, no iLok, 3 machines, on macOS (VST3, AU, AAX) and Windows (VST3). It is our plugin, it is monophonic-only, and if your source is a full mix it is the wrong tool - the free demo will tell you inside five minutes.
The TALLBOY page has A/B audio of one vocal, one synth and one drum loop through the shipping presets. Free demo on macOS and Windows.
Try TALLBOY Free Get TALLBOY - $20