Open Source vs Free Software vs Freeware: What's the Difference?
The precise difference between open source, free software, and freeware. Freeware is the one people confuse most: free to install does not mean the code is open.
Three terms, three different ideas, and most people use them interchangeably. Open source, free software, and freeware all describe software you can get without paying, but they sit in different categories with different legal and philosophical baggage. Here is the clean version.
Freeware is the easy one, and the one people most often confuse with open source. Freeware is proprietary software distributed at no cost. The company keeps the source code private, and you get a license to use the program, usually with restrictions. You cannot see how it works, you cannot modify it, and you cannot redistribute your copy. Google Chrome, WhatsApp, and Zoom are freeware. Free to download, closed code. Freeware is free like a free sample, a marketing decision, not a commitment to openness.
Free software is a movement, not just a licensing category. Richard Stallman defined it in the 1980s and the Free Software Foundation maintains it. The "free" means freedom, not price. Stallman's four freedoms: run the program for any purpose, study and modify the source, redistribute copies, and distribute your modified versions. Software counts as free software if its license grants all four. The point is political: free software exists so users control their computers instead of being controlled by vendors.
Open source is the term a group of people who disliked the political framing came up with. In 1998, Eric Raymond, Bruce Perens, and others took the same body of software and rebranded it around practical and technical benefits, the idea that a visible development process produces better, more reliable code. The Open Source Definition, based on the Debian Free Software Guidelines, lists the criteria: free redistribution, source code available, modifications allowed, no discrimination against people or fields of endeavor, and licenses that do not restrict other software.
The important part: free software and open source describe almost exactly the same set of programs. The GPL, MIT, and Apache licenses all satisfy both definitions. The difference is why people use the terms, not which software they point at. Stallman and the FSF say "free software" and mean a moral position about user rights. The open source movement says "open source" and means an engineering method. Every free software license is also open source, and nearly every open source license is also free software. The disagreements happen at the edges.
Freeware is the odd one out. It is closed source, so it can never be free software or open source. A freeware program can change status later if the company releases its source, but while it ships as freeware, it is proprietary. This is the mistake that keeps happening: a free app is not an open source app. Freeware means priced at zero and nothing more.
A comparison:
| Term | What it guarantees | Example |
|---|---|---|
| Open source | Source code is public; a license lets you use, modify, and redistribute it | PostgreSQL, React, Linux |
| Free software | The same four freedoms, framed as a user-rights movement | GNU utilities, GPL programs |
| Freeware | Nothing beyond a free price; source stays closed | WhatsApp, Chrome, Zoom |
Apply two questions to any tool. Can I see the source code? Can I modify and redistribute it? Yes to both means open source and almost certainly free software. No to both, but it costs nothing, means freeware. The difference matters when you build: only open source code is legally reusable, and only under its license terms. Freeware gives you nothing to reuse. My guide to how open source licensing works walks through the licenses themselves and what each one allows.