Why TinyTask Portable Is Just TinyTask

Two files in one folder, and that is the entire footprint.

The executable is the program. Beside it sits a small settings file holding your preferences, created the first time you run it. Nothing else is written anywhere on the machine.

That means no installation step, no administrator rights needed to set it up, and nothing left behind when you delete it. Removing it is deleting two files, as covered on the uninstall page.

It also means your settings live with the program rather than with the computer. Your hotkey, your playback speed, your loop count, all in that one file. What is in it is covered on the settings file page.

Copy the executable to the stick. Run it from there. That is the whole procedure.

The settings file gets created on the stick alongside the program, so your preferences travel with it. Plug into another machine and everything is set up the way you left it.

Keep your saved recordings on the stick too, in a folder next to the program. They are separate files and nothing links them to the executable automatically. If you leave them on your own machine, you arrive somewhere else with a macro player and no macros.

One caution about drives. If the stick is write protected, or you are running from inside a compressed archive without extracting first, the program cannot save your settings. It will run, and your preferences will quietly reset every time. Extract properly and use a writable drive.

Three assumptions get attached to the word, and all three are wrong here.

It does not mean cross-platform. Portable describes installation, not operating systems. This is a Windows program on every drive you put it on. It will not run on macOS, and the Mac page covers what to use there instead.

It does not mean your macros are portable. This is the important one and almost nobody says it. A recording replays screen positions. Move to a machine with a different screen size, a different scaling setting or a different window layout, and every click lands somewhere else. The program travels perfectly. Your macros do not.

It does not mean it will run everywhere you plug it in. Managed work computers frequently block programs from running off removable drives, or from anywhere outside approved folders. That is a policy on the machine, not a fault in the program, and there is no way around it from your side.

If you genuinely need one macro to work on more than one machine, these habits do most of the work.

Maximise the window you are automating before you record. A maximised window sits in a predictable place on any screen. A restored window does not.

Use keyboard steps instead of clicks wherever the task allows. Keys do not depend on screen position at all, so they survive resolution changes completely.

Start every macro from the same visible state. Record it opening the application itself rather than assuming a window is already there.

Test on the target machine before you rely on it. Watch it run once. If clicks are landing in the wrong places, the not working page covers the causes.

You will find downloads with portable in the file name. Treat them carefully.

There is nothing for them to be. No separate portable build exists. A file named that way was renamed by whoever is hosting it, and you have no way of knowing what else changed at the same time.

The protection is simple and it is the same one we apply to our own files. Compare the checksum of what you downloaded against the published one. Ours is on the download page, and how to run the check is on the safety page. If it matches, you have the real file regardless of what the file was called. If it does not, delete it.

A claim circulates about this program that is simply false, and it usually appears on pages about the portable version.

You cannot pause a recording, fix something, and continue. There is no pause. Pressing the record hotkey again ends the recording. If you make a mistake halfway through, you record it again from the start.

That sounds like a small thing. It is not. Someone following that advice presses the key expecting a pause, gets a finished recording instead, and then wonders why their macro is half the length it should be. Recording properly is covered in the how to use TinyTask guide.