Prime95 Portable: Run It From Any Folder or USB Drive

Quick facts: Prime95 30.19 build 20 is portable by design. There is no installer for the standard Windows package, no administrator account is required for normal use, and the program keeps its settings and logs in the same folder as the executable. Extract the official zip to a writable folder and double-click prime95.exe. On Linux and macOS the command-line mprime follows the same extract-and-run pattern. Portable here means the official program’s normal behaviour, not a separate repackaged edition from a third-party site.

What portable means for Prime95, exactly

Many programs install services, scatter settings across the registry and user profile, and require an uninstaller. Prime95 does none of that for a normal stress test. Its folder contains the executable, its supporting libraries, its documentation, and, after you run it, the files it creates for itself: prime.txt for current settings, results output, and work-related files if you join GIMPS. Move the whole folder and you move the setup. Delete the whole folder and a test-only setup is gone. That design is why technicians carry Prime95 on a USB drive between machines, and why the most important setup rule is not installation at all, but choosing a folder the program can write to.

Set up a portable copy correctly

Download the verified package from the download page and check its SHA-256 if the copy will travel between machines. Extract the full contents to a new folder; do not run the executable from inside the zip viewer, and do not use an extraction wizard’s default temporary folder, a trap the program’s own readme warns about in effect by requiring a writable directory. The extracted folder needs to stay writable because the program writes prime.txt and result logs as it runs. On Windows, a folder in Documents, on a data drive, or at the root of a USB drive all work. A folder under Program Files is a poor choice because normal user accounts may not be able to write there without elevation, which defeats the no-administrator simplicity of portable use.

Using one copy on several machines

A USB copy is convenient, but treat each machine’s results separately. Copy or rename the results file after a run, or keep a small text note per machine recording the date, preset, duration, and outcome, because the folder’s logs otherwise blend together. Remember that settings in prime.txt travel with the folder: worker counts and AVX switches set for one processor may not be the choices you want on the next machine. The switches that disable AVX paths, for example, live in prime.txt, so a travelling folder can silently carry an AVX-off configuration to a new test. Before each machine’s run, open prime.txt, confirm it reflects the test you intend, and check that the folder still contains the complete set of library and data files from the original extraction. A partial copy is the most common portable failure, and it looks like a program fault when it is really a missing-file fault.

Configuration files: prime.txt and the old local.txt name

Current versions store settings in prime.txt. Older guides refer to local.txt because settings lived there in the past; the change notes for version 30.11 record the migration to prime.txt. If you find both names discussed in a forum thread, check the version the thread is about before copying its advice. For a portable folder this matters practically: when you back up a configuration you want to keep, back up prime.txt together with your results log. When you want a truly clean start on a new machine, extract a fresh copy from the verified zip rather than deleting files from a travelled folder one by one, so no stale setting survives unnoticed.

Checking a portable copy before you trust it

Before a portable copy earns a place on your diagnostic drive, prove it once on a machine you know well. Extract it fresh, run a short Torture Test, stop it from the menu, and confirm that prime.txt and the results output appeared in the folder and contain the run you just made. That five-minute check verifies the copy is complete, the folder is writable, and the settings file is the one the program is actually using. Repeat the check after you copy the folder to a different drive, because a copy interrupted halfway can leave a library behind. Label the drive folder with the version, 30.19 build 20, so a future copy is never confused with an older travelled folder whose prime.txt may hide settings from a different era of the program.

Limits of portability

Portable does not mean permission-free in every environment. Prime95’s readme is explicit that you should get permission from the employer or network administrator before running it on a workplace machine, and that rule applies with extra force to a USB copy brought from outside. A stress test also loads the power supply and cooling system hard; do not run it on a machine whose owner has not agreed, on a laptop running on a low battery, or on a system already showing hardware faults you have not backed up. Finally, portability does not extend across operating systems: the Windows folder will not run on Linux or macOS. Carry the separate mprime packages for those platforms if you service mixed machines, each in its own extracted folder.

A tidy portable routine

Keep the original verified zip in a separate archive folder. For each job, extract a clean copy, run the test, save the results and a settings note with the machine’s name, then archive or delete the working copy. That routine keeps checksums trustworthy, settings intentional, and evidence clear, which is the entire point of a portable diagnostic tool.

Next steps

Follow the full workflow in How to Use Prime95, choose settings from the tutorials hub, and get fresh packages only from the download page.