WinUAE Setup: Amiga Emulation in 13 Steps [2026]

WinUAE just quietly passed version 6.0.3, and the open-source Amiga emulator for Windows remains the deepest, most configurable way to run Commodore’s 16/32-bit machines on modern hardware. If you have ever tried to get a Workbench disk booting, load a WHDLoad-packed game, or figure out which Kickstart ROM an A1200 setup actually needs, you already know the learning curve is steeper than most retro emulators. This tutorial walks through the entire process end to end: installing WinUAE 6.0.3, sourcing Kickstart ROMs the legal way, building a working A500 and A1200 configuration, mounting floppy disk images, setting up a WHDLoad hard drive, mapping a controller, and tuning JIT and display filters so games actually run at the right speed.

By the end you will have a reusable WinUAE configuration file, a working game library folder structure, and a troubleshooting checklist for the errors that trip up almost everyone on their first attempt. This guide covers Windows specifically, since that is WinUAE’s primary platform, though a macOS/Linux pre-release build now exists through a community fork on GitHub.

Why bother with a 1980s computer platform in 2026? Partly preservation: a huge share of the Amiga’s software catalog, including commercial games whose publishers no longer exist, only survives because communities keep disk images and WHDLoad packages maintained. Partly performance curiosity: the Amiga’s custom chipset split graphics, sound, and CPU work in ways no modern console does, and getting that balance right in software is still a genuinely interesting technical puzzle. Either way, a correct WinUAE setup is the gateway to all of it, and getting the fundamentals right the first time saves hours of guesswork later.

What Is WinUAE and Why Amiga Emulation Still Matters in 2026

WinUAE (Windows Unix Amiga Emulator) is a cycle-accurate emulator for the Commodore Amiga line, released under the GNU GPL version 2. It reproduces the Amiga’s custom chipset, the Paula sound chip, and the 68000-series CPU family closely enough that demoscene productions, which rely on exact hardware timing, still run correctly decades after the real machines stopped shipping. That accuracy is the whole reason WinUAE setup remains a popular search topic even in 2026: cheaper, friendlier front ends exist, but none match WinUAE’s raw configuration depth when something needs to behave exactly like real Amiga hardware.

The Amiga catalog itself is why people keep coming back. Workbench productivity tools, AmigaOS demos, and a library of genre-defining games built around the Amiga’s custom chipset still attract both nostalgia-driven players and preservationists. WHDLoad, a community-built compatibility layer, converts most of that floppy-based library into hard-drive-installable packages, which removes the tedious disk-swapping that made original Amiga hardware painful to use for long sessions. Pair WHDLoad with WinUAE’s JIT compiler and a modern x86 CPU, and software that once ran on a 7MHz 68000 chip now launches in under a second.

WinUAE also sits at the center of a small but active ecosystem. Cloanto’s commercial Amiga Forever bundles licensed Kickstart ROMs with a simplified front end, FS-UAE focuses on cross-platform game library management, and front ends like WinUAELoader add controller-first navigation on top of WinUAE’s own engine. Picking the right tool depends on how much manual configuration you are willing to do, which this guide covers later alongside a full feature comparison.

How WinUAE’s Cycle-Accurate Emulation and the Paula Chip Actually Work

Understanding why WinUAE setup involves so many tabs helps the configuration steps make sense later. A real Amiga split work across three major subsystems: the 68000-series CPU for program logic, a custom chipset (Agnus and Denise, later folded into the AGA chipset on A1200/A4000 machines) for graphics and DMA memory access, and Paula for sound, disk control, and some I/O. These subsystems ran in lockstep at precise clock cycles, and a huge amount of Amiga software, especially demos and some games, directly depends on that exact timing rather than treating the chipset as an abstract graphics API.

WinUAE’s cycle-exact modes reproduce that timing instruction by instruction, which is computationally expensive but is the only way to guarantee a demoscene production or a copy-protection check behaves exactly as it did on 1990s hardware. JIT compilation trades some of that precision for raw speed by translating blocks of 68k instructions into native x86 code ahead of execution, which is why this guide treats JIT as a per-task decision rather than a setting you flip once and forget. Paula’s sound emulation follows the same logic: accurate emulation reproduces period-correct audio artifacts, while simplified audio paths prioritize smoothness on the host PC’s sound driver.

Prerequisites: Versions, Hardware, and What You Need Before Starting

Before starting the WinUAE setup, gather the following. None of this requires paid software beyond the optional licensed Kickstart ROM package.

WinUAE 6.0.3 (the current stable release as of March 2026), downloaded as either the 64-bit installer or the 64-bit ZIP archive from the official SourceForge project page
Windows 10 or Windows 11, 64-bit — WinUAE’s current official packaging targets 64-bit Windows
A modern x86 CPU — any recent Intel or AMD processor comfortably handles JIT-accelerated 68020/68040 emulation; the heavier lifting is only needed for RTG graphics modes and high core-count demoscene productions
At least one legally obtained Kickstart ROM file matching the Amiga model you want to emulate (A500, A600, A1200, A4000, or CD32)
Disk image files in .adf format for floppy-based software, or WHDLoad packages for hard-drive installs
A USB game controller or keyboard, since many Amiga games expect a one- or two-button joystick layout
Roughly 2-5 GB of free disk space for the emulator, ROMs, and a virtual hard drive image (an HDF file)

The single most important prerequisite is the Kickstart ROM. WinUAE is free and open source, but it cannot legally include Commodore’s firmware. The next section covers the three lawful ways to obtain it before any of the configuration steps begin.

Note that WinUAE’s official documentation does not publish a single formal minimum-spec table the way a modern game does. In practice, the bottleneck for basic floppy-game emulation is close to zero on any PC built in the last decade; the areas where hardware actually matters are JIT-accelerated 68040 workloads, RTG graphics modes running at higher resolutions than the native chipset, and running multiple WinUAE instances side by side. If your PC runs any current web browser comfortably, it can run WinUAE’s core emulation without issue — the configuration work in this guide is the actual hard part, not the hardware.

Step 1-2: Download and Install WinUAE 6.0.3

Head to the official WinUAE SourceForge download page and pick the 64-bit installer unless you have a specific reason to run the 32-bit build (older hardware or a legacy script that expects 32-bit paths). The installer handles registry entries and file associations automatically; the ZIP archive is a fully portable option if you want to run WinUAE from a USB drive or avoid touching the Windows registry.

Run the installer and accept the default install path unless you have a dedicated emulation drive. Once installed, launch WinUAE for the first time. You will land on the GUI’s main configuration panel, organized into tabs: CPU and FPU, Chipset, ROM, RAM, Floppy drives, Hard drives, Display, Sound, Input, and Miscellaneous. Every setting you will touch in this guide lives in one of those tabs.

# Typical WinUAE 64-bit install paths
C:Program FilesWinUAEwinuae64.exe
C:Program FilesWinUAEwinuae64.ini     (default config, do not edit directly)

# Portable ZIP layout (recommended for a self-contained game library)
D:RetroAmigaWinUAEwinuae64.exe
D:RetroAmigaRoms
D:RetroAmigaFloppies
D:RetroAmigaHDF

Creating a dedicated folder structure before you configure anything else makes long-term maintenance much easier, especially once you have a dozen WHDLoad games and several Amiga model configs saved. A WinUAE beginner’s guide hosted on retroprojects.de recommends exactly this approach: get the folder layout right before touching ROM paths, because WinUAE’s ROM scanner and hard-drive mounting both reference absolute paths that are painful to fix later.

Several community guides walk through this same installation flow and converge on the same basic advice. A short setup walkthrough on ale.emuunlim.com opens with a reassurance worth repeating here: “This tutorial will show you how to setup WinUAE quickly and easily.” The install itself genuinely is the easy part — double-click the installer or unzip the portable build, and WinUAE is ready to open. The time investment in a WinUAE setup is almost entirely in the configuration steps that follow, not the installation itself.

Step 3: Source Kickstart ROMs the Legal Way

Kickstart ROM images are copyrighted Commodore/Amiga firmware, not open-source code, which means downloading them from unlicensed ROM sites is not a legitimate path for a WinUAE setup. There are three lawful routes, and the guide from EmulationKing’s WinUAE reference page lists the first two as the standard options most users rely on:

Dump the ROM from Amiga hardware you own, using a tool such as grabkick run on the real machine, then transfer the resulting image to your PC
Buy Cloanto’s Amiga Forever package, which bundles licensed Kickstart versions including 1.3, 2.04, and 3.1, along with a curated software library and a simplified launcher
Use AROS ROM replacements, a free, open-source reimplementation of AmigaOS/Kickstart that runs a meaningful subset of Amiga software, though it is not fully compatible with everything built against the original firmware

Once you have a legally sourced ROM file, drop it into the Roms folder you created in Step 1. Open WinUAE, go to the ROM tab, point the ROM path at that folder, and click the rescan option so WinUAE indexes the file. WinUAE identifies a main ROM and, for CD32 configurations specifically, an extended ROM — the command-line equivalents are the -r flag for the main Kickstart image and -K for the extended CD32 ROM, which is worth knowing if you ever script batch launches.

Amiga Model	Typical Kickstart Version	Best Suited For
A500	1.2 or 1.3	Most floppy-based games from the mid-to-late 1980s
A600	2.0 / 2.05	Early-1990s software with ECS chipset requirements
A1200	3.0 or 3.1	AGA-era games, 68020 software, many WHDLoad packages
A4000	3.0 or 3.1	Productivity software, 68040 demos, high-end AGA titles
CD32	CD32 main ROM + CD32 extended ROM	CD-based Amiga console software

If you are unsure where to start, an A500 configuration with Kickstart 1.3 is the safest entry point for classic disk-based games, while an A1200 setup with Kickstart 3.1 covers the bulk of WHDLoad’s modern game library.

Step 4-5: Configure Your First Amiga Model and Memory Settings

With a ROM in place, open the Quickstart tab (or the manual Chipset/CPU tabs if you prefer full control) and pick the Amiga model you want to emulate. WinUAE ships with presets for A500, A500+, A600, A1200, A4000, and CD32, each of which automatically sets a sane chipset, CPU, and memory baseline. Starting from a preset and adjusting from there is far less error-prone than building a configuration from a blank CPU tab.

Memory configuration is where most new users either under- or over-provision. Chip RAM is the memory the Amiga’s custom chipset can directly access for graphics and sound; Fast RAM is additional memory the CPU can use but the chipset cannot. Getting this wrong causes crashes in software that checks for a specific memory layout.

A500-class setups: 512 KB to 1 MB Chip RAM, matching the original hardware’s common expansion level
A1200/A4000-class setups: 2 MB Chip RAM, which matches the AGA-era hardware most late Amiga software expects
Add Fast RAM (8-64 MB is reasonable) when running Workbench, WHDLoad front ends, or any productivity software — pure floppy games rarely need it

Save this as its own configuration before moving on. WinUAE’s Configurations panel lets you store named presets — “A500-Games,” “A1200-WHDLoad,” “CD32” — so switching between Amiga models later is a two-click operation instead of rebuilding settings from scratch every session.

Step 6: Mount Floppy Disk Images (ADF Files)

Classic Amiga software ships as .adf disk image files, each representing a single 3.5-inch floppy disk. In the Floppy drives tab, click the drive slot (DF0: is the primary drive almost every piece of Amiga software expects to boot from) and browse to your disk image. Multi-disk games need their additional disks inserted into DF0: when the game prompts for a disk swap, which WinUAE handles instantly compared to physical disk swapping on real hardware.

A WinUAE guide mirrored on arcadecontrols.com walks through this exact floppy-mounting workflow and is a useful secondary reference if your disk image refuses to boot — the most common cause is an incorrect drive type setting (WinUAE defaults to a standard 3.5″ DD drive, which covers the vast majority of the Amiga library).

# Command-line floppy mount example (useful for batch-launching specific titles)
winuae64.exe -s floppy0=D:RetroAmigaFloppiesShadowOfTheBeast.adf -s use_gui=no

# Multi-disk games: insert disk 2 when prompted, same drive slot
winuae64.exe -s floppy0=D:RetroAmigaFloppiesMonkeyIsland_Disk1.adf

If a floppy game loads but crashes partway through, double-check that the disk image file is not corrupted and that you are using the correct regional version — European PAL releases and US NTSC releases of the same game sometimes expect slightly different chipset timing, which WinUAE’s region setting controls.

Step 7-8: Create an HDF Hard Drive and Install WHDLoad

WHDLoad is the community project that converts floppy-based Amiga software into hard-drive installs, eliminating disk swapping and adding compatibility patches for timing-sensitive games. To use it, WinUAE needs a virtual hard drive, represented as an HDF file.

In the Hard drives tab, click Add Hardfile, choose a size (1 GB is ample for a long-running WHDLoad library according to community setup guides, though a larger library of AGA-era games benefits from more headroom), and point WinUAE at a new .hdf file in your HDF folder. Boot into Workbench using your Kickstart 3.1 configuration, format the new hard drive from within AmigaOS, then copy WHDLoad’s core files and your game packages onto it.

# Typical WHDLoad game folder structure once installed on the HDF
DH0:WHDLoad/
DH0:WHDLoad/C/WHDLoad
DH0:Games/Workbench/
DH0:Games/ShadowOfTheBeast/ShadowOfTheBeast.slave
DH0:Games/ShadowOfTheBeast/ShadowOfTheBeast.info

# Launching a WHDLoad game from the Amiga CLI
cd DH0:Games/ShadowOfTheBeast
WHDLoad ShadowOfTheBeast.slave

Most WHDLoad game packages include a .slave file alongside documentation and an icon; running the slave file through WHDLoad applies the game-specific patch set that fixes copy-protection checks and timing bugs that would otherwise fail under emulation. CD32 titles and most hard-drive-based installs both require this HDF step — floppy-only games can skip it entirely if you are happy with disk-swapping.

Step 9: Map Controllers and Keyboard Input

Most Amiga games expect a simple one-button joystick in Port 2, though some two-player titles use both ports simultaneously. Open the Input tab, select your USB controller from the device list, and map its analog stick or D-pad to the four directional inputs, then map a face button to the primary fire button. WinUAE also supports autofire toggling and dead-zone adjustment for analog sticks that drift.

Map your controller to Joystick Port 2 for the overwhelming majority of single-player games
Configure a second controller on Port 1 only for two-player titles that specifically request it
Keep a keyboard mapping active for Amiga-specific keys (Amiga key, Help key, function row) since some software and most Workbench navigation still expects them
Third-party front ends like WinUAELoader add deeper controller-first remapping if you are building a dedicated arcade-style cabinet rather than a desktop setup

Save the input profile alongside your model configuration. WinUAE lets input mappings persist per saved configuration, so an A500-Games profile and an A1200-WHDLoad profile can each remember a different controller layout without you reconfiguring anything between sessions.

Step 10-11: Tune Display Filters, Audio, and JIT Performance

WinUAE supports JIT compilation, which translates emulated 68020/68030/68040 instructions into code the host CPU runs more directly, rather than interpreting each instruction cycle by cycle. Enable it in the CPU tab when you want faster Workbench responsiveness, smoother RTG graphics modes, or better performance in CPU-heavy demos and productivity software. Strict cycle-exact or non-JIT settings remain the better choice for compatibility testing or for timing-sensitive demoscene productions, since JIT occasionally diverges from exact hardware timing.

On the Display tab, you have a trade-off between authenticity and a cleaner modern look. Integer-style scaling with minimal filtering and accurate chipset timing reproduces what the game actually looked like on a CRT; bilinear scaling with scanline-style overlays gives a smoother, more modern-looking picture at the cost of some pixel precision. On the Sound tab, accurate Paula chip emulation preserves the Amiga’s distinctive audio character, while disabling excess host-side audio processing generally keeps the sound closer to the original.

Setting	Accuracy-First Choice	Performance-First Choice
CPU Emulation	Cycle-exact, JIT disabled	JIT enabled
Display Scaling	Integer scaling, no filtering	Bilinear scaling, scanline overlay
Chipset Timing	Cycle-exact chipset	Immediate/fast chipset
Audio Processing	Direct Paula emulation	Reduced-latency audio buffer
Best For	Demos, trackers, compatibility testing	General gameplay, Workbench use

If a game runs noticeably too fast, inconsistently, or with garbled audio, it is almost always one of these settings fighting the software’s expectations rather than a WinUAE bug — the troubleshooting section below has the specific fixes for each symptom.

Step 12-13: Save Configurations and Organize Your Game Library

Once a configuration behaves the way you want, click Save config at the bottom of the panel. A WinUAE beginner’s guide from retroprojects.de, referenced earlier in this tutorial, puts the payoff of this step plainly: “Then click Save config at the bottom of the panel. This way, next time you only need Configurations → Load and your setup starts.” Every ROM path, memory setting, controller map, and display filter comes back exactly as you left it. This single habit is what turns WinUAE from a fiddly one-off emulator session into a reliable retro gaming setup you can return to in seconds.

It is worth saving at least two variants of any given configuration once your library grows: one tuned for accuracy (JIT off, cycle-exact chipset, direct Paula audio) and one tuned for speed (JIT on, turbo CPU, reduced-latency audio). Loading the wrong variant for a given piece of software is a common source of “it worked yesterday” confusion, and keeping both variants named clearly avoids it entirely.

For a library beyond a handful of games, organize disk images and WHDLoad packages by machine type and genre rather than dumping everything into one folder. A flat folder works for five games; it becomes unmanageable past twenty. Name configuration files to match their purpose — “A500-ActionGames.uae,” “A1200-WHDLoad-Platformers.uae” — so you are not guessing which saved config boots which library.

# Recommended long-term folder layout
D:RetroAmiga
  ConfigsA500-Games.uae
  ConfigsA1200-WHDLoad.uae
  ConfigsCD32.uae
  Romskick13.rom
  Romskick31.rom
  FloppiesActionGames
  FloppiesAdventure
  HDFA1200-WHDLoad.hdf
  HDFCD32-Games.hdf

This structure scales cleanly whether you end up with ten games or several hundred, and it makes backing up your entire library (HDF files, saved configs, and legally sourced ROMs) a matter of copying one parent folder.

WinUAE vs FS-UAE vs Amiga Forever: Choosing the Right Tool

WinUAE is not the only option for Amiga emulation, and it is worth knowing where it fits before committing to the deeper configuration work this guide covers. FS-UAE targets the same UAE emulation core but wraps it in a more streamlined, game-library-oriented interface that works the same way across Windows, Linux, and macOS. Amiga Forever is Cloanto’s commercial package: it bundles licensed Kickstart ROMs, a curated software library, and a simplified launcher aimed at users who want a working setup without sourcing ROMs themselves.

Factor	WinUAE	FS-UAE	Amiga Forever
Platform Focus	Windows	Cross-platform (Windows, Linux, macOS)	Windows-oriented, broader support varies by edition
Configuration Depth	Very extensive — chipset, CPU, timing, display, sound, storage, input all exposed	Streamlined, game-launcher focused	Integrated, limited manual tuning
Kickstart ROMs	User-supplied	User-supplied, some AROS workflows	Licensed ROMs included
WHDLoad Support	Strong, manual setup	Strong, library-oriented workflow	Integrated, convenience-focused
Licensing	Free, GPLv2	Free, open source	Commercial purchase required
Best Suited To	Accurate, highly configurable emulation	Easier cross-platform game launching	Beginners wanting licensed content out of the box

If you already own real Amiga hardware and can dump your own Kickstart ROM, or you specifically want the deepest possible control over chipset timing, WinUAE is the right tool, and everything in this guide applies directly. If you want to skip ROM sourcing entirely and get licensed content running in minutes, Amiga Forever trades configuration depth for convenience. FS-UAE sits in between, useful if your retro gaming setup needs to work identically across more than one operating system.

5 Common Pitfalls When Setting Up WinUAE

These are the mistakes that derail a WinUAE setup most often, almost always on the first attempt before a working configuration gets saved.

Downloading ROMs from unlicensed sites. Beyond the legal problem, these files are frequently mislabeled, corrupted, or bundled with unwanted extras. Dump your own hardware, buy Amiga Forever, or use AROS replacements instead.
Mismatching the Kickstart version to the Amiga model. Booting an A1200/AGA configuration with a Kickstart 1.3 ROM (built for the original A500 chipset) will fail outright or behave unpredictably. Match the ROM table above exactly.
Skipping the dedicated folder structure. Scattering ROMs, ADF files, and HDF images across random folders makes WinUAE’s absolute-path ROM scanner and hard-drive mounts break the moment you move or rename a folder later.
Enabling JIT for timing-sensitive software. JIT is excellent for Workbench and most games, but demos, trackers, and copy-protection-heavy titles can behave incorrectly under JIT. Keep a non-JIT, cycle-exact configuration saved separately for this category.
Forgetting to save the configuration at all. Spending twenty minutes getting memory, display, and controller settings right and then closing WinUAE without clicking Save config means redoing all of it next session.

Troubleshooting WinUAE: 8 Common Errors and How to Fix Them

The ale.emuunlim.com guide referenced earlier notes that WinUAE setup is meant to be quick and easy once the basics click, and in practice nearly every stumbling block traces back to one of these eight issues.

“No Kickstart ROM found” or the emulator refuses to boot. The ROM path is not configured, points to the wrong folder, or the file itself is an unsupported format. Re-check the ROM tab’s path setting and rescan.
Wrong machine/ROM combination. An A1200 or CD32 profile paired with an incompatible ROM version will fail to boot or crash software mid-run. Confirm the Kickstart version matches the model table above.
CD32 configuration won’t boot at all. CD32 emulation specifically needs both a main ROM and an extended ROM configured — a single ROM file is not enough for this model.
WHDLoad games fail to launch. This is usually insufficient Fast RAM, a missing or incomplete hard-drive setup, missing WHDLoad core files on the HDF, or an incorrect Kickstart version for that specific game package.
Games run too fast, or input lags behind the action. JIT, aggressive turbo CPU settings, or an inaccurate chipset timing mode is the usual cause. Switch to cycle-exact chipset timing and disable JIT for that specific title.
Black screen or garbled graphics after booting. Check the chipset selection (OCS/ECS/AGA) against what the software expects, and verify the display scaling mode is not clipping the visible screen area.
Floppy disk images fail to load or the game freezes on a disk-swap prompt. Confirm the ADF file is not corrupted, that you are using the correct regional release (PAL vs NTSC), and that the floppy drive type matches a standard 3.5″ DD drive unless the software specifically calls for something else.
Audio crackles, stutters, or is out of sync with on-screen action. Lower the audio buffer size for latency-sensitive software, or raise it slightly if you are hearing dropouts rather than lag — this is a balancing act specific to your host PC’s audio driver.

Example output when a ROM path is misconfigured looks like this in WinUAE’s log panel:

ROM: Scanning D:RetroAmigaRoms ...
ROM: 0 ROM(s) found, 0 valid.
ERROR: Kickstart ROM required for selected Amiga model.
Boot sequence halted.

That exact message means the ROM tab’s path is wrong, empty, or pointed at a folder with no valid ROM file — not a corrupted WinUAE install, which is the first (incorrect) assumption most new users make. For comparison, here is what a healthy boot sequence looks like once the ROM path, model, and memory settings are correct:

ROM: Scanning D:RetroAmigaRoms ...
ROM: 1 ROM(s) found, 1 valid.
ROM: Loaded kick31.rom as main Kickstart (A1200/A4000 compatible)
CHIPSET: AGA selected, 2048K Chip RAM configured
MEMORY: 32768K Fast RAM configured
Boot sequence started.
Workbench 3.1 loaded successfully.

If your log output resembles the second example rather than the first, the configuration is sound and any remaining problem is specific to the software you are trying to run rather than the base WinUAE setup.

Advanced Tips: JIT Tuning, RTG Graphics, and Multi-Core Hosts

Once the basic setup is reliable, a few advanced options unlock meaningfully better performance and compatibility. RTG (Retargetable Graphics) support, implemented through Picasso96-compatible configurations, lets AmigaOS use a modern graphics card for higher resolutions and color depths than the native chipset ever supported — useful for productivity software and later AmigaOS releases, though most classic games do not use or benefit from it.

On multi-core host systems, WinUAE does not meaningfully parallelize a single emulated Amiga across cores, since Amiga emulation is inherently a mostly single-threaded workload tied to precise timing. What multiple cores do help with is running several WinUAE instances simultaneously — useful if you are testing a WHDLoad package against both a 68000-based A500 profile and a 68040-based A4000 profile side by side, or if you are streaming gameplay while the emulator runs.

Use the fastest possible JIT and turbo CPU settings only for Workbench navigation and file management, then switch to a game-specific saved configuration before launching software
Keep separate HDF files for different software categories (a games-only HDF and a separate productivity/Workbench HDF) so a corrupted game installer cannot take down your entire library
For demoscene productions specifically, disable JIT and use cycle-exact chipset and CPU settings — these productions are built to exploit exact hardware timing, and anything less than cycle accuracy can visibly break the effect
If you plan to eventually run WinUAE outside Windows, note that a macOS/Linux pre-release build exists through a community GitHub fork (reinauer/WinUAE, tagged unix_r1), though it is not the official Windows release and should be treated as experimental

Complete Working Project: A Portable Amiga Retro Station

With every step above completed, here is how they combine into one finished, reusable project: a portable Amiga retro gaming station that runs entirely from a single external drive.

Install the WinUAE 6.0.3 64-bit ZIP build (not the installer) directly onto an external SSD so the entire emulator is portable across any Windows PC
Build two saved configurations: an A500-Games profile with Kickstart 1.3 and 1 MB Chip RAM for classic floppy titles, and an A1200-WHDLoad profile with Kickstart 3.1, 2 MB Chip RAM, and 32 MB Fast RAM for the WHDLoad library
Create a single 4 GB HDF file for the A1200 profile, formatted in Workbench, loaded with the WHDLoad core and a curated set of legally owned WHDLoad game packages
Map a single USB controller to Joystick Port 2 across both saved configurations so the same gamepad works regardless of which profile is loaded
Set the A500 profile to cycle-exact chipset timing with JIT disabled (for maximum compatibility with older, timing-sensitive floppy games) and the A1200 profile to JIT-enabled turbo mode (for faster WHDLoad load times)
Save both configurations to the external drive alongside the ROMs, ADF files, and HDF image, so the entire station — emulator, ROMs, games, and settings — moves with the drive

Plug that external drive into any Windows 10/11 PC, launch winuae64.exe directly from it, load whichever saved configuration matches what you want to play, and the entire Amiga library boots exactly as configured — no reinstalling, no re-mapping controllers, no re-sourcing ROMs. This is the practical payoff of treating configuration saving and folder structure as first-class steps rather than afterthoughts.

Is WinUAE Still Actively Maintained Going Into 2026?

Yes, and that is part of why a WinUAE setup guide is still worth writing in October 2026. The 6.0.3 release landed in March 2026, the project’s official SourceForge download page itself received an update as recently as September 2026, and a dedicated GitHub repository tracking WinUAE’s changelog has stayed active throughout the year. None of that activity points to a newer Windows release beyond 6.0.3 as of this writing, but it does confirm the project has not gone dormant the way some long-running emulators eventually do.

That ongoing maintenance matters for a practical reason: WinUAE’s accuracy work is incremental. Each release tends to fix specific chipset edge cases, add support for obscure expansion hardware configurations, or improve JIT compatibility with particular CPU models, rather than overhauling the emulator wholesale. If a specific WHDLoad title behaves oddly on 6.0.3, checking the changelog for a newer point release before assuming your configuration is wrong is a reasonable first troubleshooting step.

Frequently Asked Questions

Is WinUAE free?
Yes. WinUAE is open-source software released under the GNU GPL version 2, and the emulator itself has never required payment. The only cost involved in a complete setup is an optional Kickstart ROM license, such as Cloanto’s Amiga Forever package, if you do not own real Amiga hardware to dump a ROM from.

What is the latest version of WinUAE as of October 2026?
WinUAE 6.0.3, released March 3, 2026, is the current stable Windows release, distributed as a 32-bit installer, a 64-bit installer, and a 64-bit ZIP archive from the official SourceForge project page.

Do I need a Kickstart ROM to use WinUAE?
Yes, at least one Kickstart ROM is required for WinUAE to boot any emulated Amiga model. There is no way around this requirement, since Kickstart is the Amiga’s equivalent of a BIOS/firmware layer that the emulator does not and cannot legally bundle.

Is it legal to download Kickstart ROMs?
Downloading Kickstart ROMs from unlicensed ROM sites is not a legitimate option, since the firmware remains copyrighted. The lawful paths are dumping a ROM from Amiga hardware you personally own, purchasing Cloanto’s Amiga Forever package for licensed ROMs, or using the free, open-source AROS ROM replacement project.

What is WHDLoad and do I need it?
WHDLoad is a community-built compatibility layer that installs floppy-based Amiga games onto a virtual hard drive, removing disk-swapping and patching timing or copy-protection issues that can otherwise cause failures under emulation. It is optional for straightforward floppy games but close to essential for CD32 titles and for running a large game library efficiently.

Should I enable JIT in WinUAE?
Enable JIT for faster Workbench use, general gameplay, and WHDLoad titles where raw speed matters more than exact timing. Disable JIT for demoscene productions, trackers, and any software that depends on precise hardware-cycle timing, where JIT can occasionally cause visible or audible glitches.

What is the difference between WinUAE and FS-UAE?
Both are built on the same underlying UAE emulation core, but WinUAE exposes far deeper manual configuration across chipset, CPU, timing, display, and input, while FS-UAE wraps the same core in a more streamlined, cross-platform, game-library-focused interface aimed at users who want less manual tuning.

Can WinUAE run on macOS or Linux?
WinUAE’s official releases and primary support target Windows. A community-maintained pre-release build for macOS and Linux exists on GitHub, but it is not the official distribution and should be treated as experimental rather than a fully supported alternative.