About

Who is behind this

FreeFullSoft is one developer, Ali Kaptanoglu, releasing the desktop applications he writes. There is no company, no team, no funding and no advertising network behind it. That is also the reason the catalogue is short: each app is written from scratch, and a small app written properly takes a while.

Why it is free

These are small, single-purpose applications. Charging for them would mean payment handling, licence keys, a support queue and an accounts system — all of it larger than the apps themselves. Giving them away costs almost nothing and means nobody has to weigh up whether a desktop toy is worth a card number.

Being free here is not a trial strategy. There is no paid tier the free version is nudging you towards, no feature held back and no "upgrade to unlock". If a larger application ever does get a paid upgrade, whatever was offered as free will stay free.

What this site is not

"Free full software" is also, unfortunately, the phrase that sites distributing cracked commercial programs use about themselves. This is not one of those sites. Every file here is software written by us. There is no pirated application, no patched installer, no keygen and no re-hosted third-party download, and there will not be. If you were looking for a cracked copy of someone's paid program, you are in the wrong place.

Platforms

macOS first, because that is where the current apps started, and Windows next. Each app's page states exactly which OS version and which chip it needs — nothing is listed for a platform it has not actually been run on.

Signing, and the warning you will see

The Mac apps are not notarised yet, which needs a paid Apple Developer membership, so macOS asks you to confirm the first launch (right-click → Open). Windows SmartScreen shows a similar notice for any installer it has not seen downloaded many times. Both are about reputation and paperwork, not about what is in the file — each app page walks through it.

Getting in touch

Bug reports are genuinely welcome and go straight to the person who wrote the code. Include your OS version and what you were doing when it went wrong.