Short answer
Pick the Rufus file by the architecture of the PC that runs it: standard x64 for most PCs, ARM64 for Windows on Arm, x86 for 32-bit Windows. The portable x64 file is the same program as the standard one; the p in its name makes it keep settings in an ini file beside the executable instead of the registry.
How do you choose the right Rufus file?
- Check your PC's architecture. Open Settings, then System, then About, and read System type: x64-based, ARM-based or 32-bit.
- Pick the matching file. Use the standard x64 file on x64, the ARM64 file on an ARM-based PC, and the x86 file on 32-bit Windows.
- Decide where settings go. Choose the portable file if settings should travel with the executable, for example on a tools USB.
- Keep one copy. Delete older copies so you always open the version you checked.
Are the standard and portable files different programs?
The standard and portable x64 downloads are the same program. On the current release both are 1.9 MB with the same SHA-256 digest, as the download page shows. What changes their behavior is the file name: at startup the program looks for a p in its own name and, if it finds one, creates a rufus.ini settings file in its folder (source). With that file present it reads and writes every setting there and uses its own folder for downloaded helper files (source).
Where does the standard file keep settings?
Without that ini file beside it, the program stores settings in the Windows registry under the current user’s Akeo Consulting key shown in the table (registry.h). That is why the standard file remembers your language and update choice wherever you move it on the same PC. If you want to remove those entries, the program’s Alt+R shortcut deletes the registry keys it created.
Which architecture do you need?
The file’s architecture must match the Windows PC that runs it. Most desktops and laptops are x64. A Windows on Arm laptop, such as one with a Snapdragon X processor, runs the ARM64 file natively. The x86 file is for 32-bit Windows and also runs on x64 through Windows’ compatibility layer. None of this limits the drive you create: an x64 PC can write an ARM64 Linux image, because the ISO decides what the drive boots.
Which file does winget use?
The winget package installs the standard file for your PC’s architecture, so a winget copy keeps its settings in the registry like a manual standard download. It adds a rufus command that you run from a new Terminal window. Keep one channel per PC: if you installed with winget, update with winget upgrade Rufus.Rufus rather than saving another copy to the desktop.
| File | Runs on | Settings stored in |
|---|---|---|
| Standard x64 | Windows x64 | HKEY_CURRENT_USER\Software\Akeo Consulting\Rufus |
| Portable x64 (name ends in p.exe) | Windows x64 | rufus.ini in the same folder |
| ARM64 | Windows on Arm | Registry, or an ini file if one sits beside it |
| x86 | 32-bit or x64 Windows | Registry, or an ini file if one sits beside it |
Frequently asked questions
Is the standard file a setup program?
No. The official site says the downloaded executable is ready to use. Standard only means it keeps settings in the registry; it does not install anything or add a Start menu entry.
Can I make the standard file portable?
Yes. The program switches to portable mode when its file name contains a p, or when a rufus.ini file already sits in the same folder. Renaming the file or creating an empty ini file of that name beside it has the same effect as the portable download.
Does the ARM64 file make ARM boot drives only?
No. The file architecture only has to match the Windows PC that runs the program. The architecture of the drive you create depends on the ISO you write, so an x64 PC can make media for an ARM64 target.