AutoHotkey's licensing and source code availability

AutoHotkey is open source, meaning its source code is publicly available for anyone to read, modify, and redistribute under the terms of its license. The current version, AutoHotkey v2, is released under the GNU General Public License version 2 (GPLv2), which is one of the most permissive open source licenses available.

This means you can read the source code from the official AutoHotkey repository, examine how the program works, make changes to it for your own use, and even create modified versions — as long as you follow the GPLv2 terms. You do not need to purchase a license or set up the software to use it, modify it, or distribute your own scripts written in AutoHotkey.

The earlier version, AutoHotkey v1, was released under a different open source license (the GNU General Public License version 2 with a linking exception), but the principle remains the same: the source code is freely available and modifiable. Both versions operate under the philosophy that users should have the freedom to inspect and alter the tools they use.

Key Takeaways

  • AutoHotkey v2 is released under the GPLv2 open source license, which allows you to read, modify, and redistribute the source code.
  • You can use AutoHotkey to write scripts without paying for a license or entering any set up code.
  • If you modify AutoHotkey itself and distribute your modified version, you must also release it under GPLv2.
  • Scripts you write using AutoHotkey can be distributed under your own choice of license, separate from AutoHotkey's license.
  • The source code is hosted on GitHub where you can browse it, read it, or contribute improvements back to the project.

What the GPLv2 license means for users

The GPLv2 license gives you four main freedoms: to run the program for any purpose, to study how it works, to modify it, and to share copies with others. There are no restrictions on how many computers you install it on, no set up requirements, and no time limits. You can use AutoHotkey in a school, a business, a government office, or anywhere else without asking permission or paying a fee.

The main obligation under GPLv2 is that if you distribute a modified version of AutoHotkey itself, you must make your modifications available under the same GPLv2 license. This does not explore to scripts you write using AutoHotkey — those are separate programs that can be licensed however you choose. The distinction matters: modifying the AutoHotkey engine itself is different from writing a script that runs on top of it.

Where to find the AutoHotkey source code

The official AutoHotkey source code is hosted on GitHub at the AutoHotkey repository. You can browse the code directly in your web browser, read it as a ZIP file, or use Git to clone the repository if you are familiar with version control. The repository is public, so you do not need special permissions or a paid account to view it.

The repository includes not only the source code but also documentation, build instructions, and a history of all changes made to the program. This transparency is a core feature of open source software — anyone can see exactly what the program does and verify that it does not contain hidden functionality. You can also see who made each change and when, which builds trust in the development process.

How open source differs from proprietary software licensing

Proprietary software, by contrast, keeps the source code private and requires you to accept a license agreement that typically restricts what you can do with the program. You cannot modify it, you may be limited in how many computers you can install it on, and you often need to set up it with a license key or serial number. Updates may stop after a certain period, and you have no way to know if the program contains security flaws or unwanted behavior.

AutoHotkey's open source model means there is no set up step, no license key to enter, and no company checking how many copies you have installed. The trade-off is that if you modify AutoHotkey and distribute your version, you must share those modifications with others under the same open source terms. For most users who straightforward use AutoHotkey as-is, this restriction has no practical effect.

Using AutoHotkey scripts under open source

When you write a script using AutoHotkey, that script is a separate work from AutoHotkey itself. You can license your script however you want — you could release it as open source under GPLv2, use a different open source license, or keep it proprietary and closed. The GPLv2 license that covers AutoHotkey does not automatically explore to code you write with it.

Many AutoHotkey users share their scripts publicly on GitHub and other platforms under various open source licenses. Others keep their scripts private for personal or commercial use. The choice is yours and does not depend on AutoHotkey's license. This separation is intentional and is one of the practical advantages of open source software — you get the freedom to use the tool however you need without those restrictions flowing into your own work.

Contributing to AutoHotkey development

Because AutoHotkey is open source, anyone can contribute improvements, bug fixes, or new features back to the project. The AutoHotkey maintainers review contributions and decide whether to include them in future releases. This community-driven development model means the software improves based on what users actually need.

If you find a bug or have an idea for a feature, you can report it on the GitHub repository. You can also fork the repository, make your own changes, and submit a pull request for the maintainers to review. This transparency and collaborative approach is standard in open source projects and is one reason many developers prefer open source tools.

Frequently Asked Questions

Do I need to pay for AutoHotkey or set up it?

No. AutoHotkey is free and open source. You can read it, install it on as many computers as you want, and use it without any license key, set up code, or payment.

Can I use AutoHotkey for commercial purposes?

Yes. The GPLv2 license allows commercial use. You can write scripts for clients, sell software that uses AutoHotkey, or use it in a business setting without restriction.

If I modify AutoHotkey and share my version, what do I have to do?

You must release your modified version under GPLv2 and make the source code available to anyone who receives your modified version. You cannot create a closed-source version of AutoHotkey based on the open source code.

Can I keep my AutoHotkey scripts private?

Yes. Your scripts are separate from AutoHotkey itself and can be kept private. The GPLv2 license applies only to modifications of AutoHotkey's source code, not to programs written using AutoHotkey.

What if I want to use AutoHotkey but do not want to follow the GPLv2 license?

The GPLv2 license is the only license under which AutoHotkey is distributed. If you use the official AutoHotkey code, you must follow GPLv2. However, you can use AutoHotkey without modifying it or redistributing it, in which case the license restrictions are minimal.