TinyTask Download With a Checksum You Can Verify

Both contain the same program. Pick whichever suits your situation.

The program file is the straightforward choice for a TinyTask download. Get it, put it where you want it, double-click. Nothing else needed.

The archive is the same program compressed. Take this one if your browser, your workplace or your security software blocks program downloads, which is common on managed machines. Extract it first. Running the program from inside an archive viewer causes problems, because the program cannot write its settings file, as the portable page explains.

There is no third option, and that is deliberate. See the section further down on what we do not host.

A small Windows program, compiled years ago and unchanged since.

Once you have it, right-click the file, choose Properties and open the Details tab. It shows the product name, the file version and the copyright, all read from inside the file rather than from its name. Those values should match what the card above says.

That is the first check, and it takes five seconds. The proper check is next.

One command, under a minute, and it works no matter where you downloaded from.

Open PowerShell in the folder holding your download and run this:

Get-FileHash .\tinytask.exe -Algorithm SHA256

Compare the result with the checksum on the card. It should match exactly, character for character. Capitals do not matter.

If it matches, you have the identical file and nothing has been added to it. If it does not, delete what you have and take a copy you can verify.

The size in bytes is a useful second check. A file meaningfully larger than the published size has had something put into it. Why any of this matters is set out on the safety page.

Nothing dramatic, which surprises people who expected an installer.

A small window opens with six buttons. That is the whole program. No setup wizard, no components to add, no restart, no administrator prompt.

The only thing it adds to your machine is one small settings file, created in the same folder the first time you run it. Delete those two files and the program is gone completely.

Windows may show a warning the first time you run it, and it may not. We could not reproduce one on a clean test machine. Either outcome is normal for a small unsigned program, and the Windows 11 page covers it.

If this is your first time with the program, the how to use TinyTask guide takes you from a blank screen to a working macro.

Every earlier version we can verify is on the versions page, each with its own size and checksum.

They are kept there rather than here for two reasons. Most people want the current build, and a page listing everything makes that harder rather than easier. And the version record carries context that does not belong on a download page, including a gap in the developer's own changelog.

Take an older build if you have a reason: an older machine, a workflow that a later release changed, or instructions written against a specific version. Newer is not automatically better with software that stopped being developed.

Three things, and each is a decision rather than an oversight.

The editor downloads. Files offered elsewhere as Micro and Standard editor versions are a different vendor's shareware, not this program. We are not going to distribute another company's paid software, and we are certainly not going to do it under this name. What they actually are, with screenshots of both, is on the with editor page.

Any setup installer. The developer's own documentation links one and that link no longer resolves. The setup file circulating under this name installs the other vendor's product, and we confirmed that by running it. If a genuine installer is ever located, it gets verified before it appears here.

Anything we cannot hash. If we cannot download a file and compute its checksum, it does not go on this page. A download list of files nobody can verify is worth nothing, and it is the exact problem this page exists to solve.

Each file's size and checksum are verified against what is on record.

If everything matches, nothing changes. If a checksum has moved, the job does not publish it. It stops and flags it for a person to look at.

That behaviour is unusual and it is deliberate. On software that has not been rebuilt in years, a changed checksum is not an update. It means the file behind the link is no longer the file that was there before. That is something to investigate, not something to pass along automatically.

The program is free to use. The developer states that macros you compile into standalone programs can be distributed and sold, with no royalties and no restrictions attached.

That last point is genuinely useful and almost nobody mentions it. What you build with it is yours, including at work and including commercially. The compile to EXE page covers how.

We do not modify, repackage or rebrand any file. The published checksum lets you verify its exact contents.