CAps™ 2.1.1

It fixes the "double caps" problem. When you hold Shift too long and end up with two capital letters at the start of a word—like COrrection or DEvice—CAps steps in and repairs them instantly. No highlighting, no fuss.

Just double-click the executable. CAps runs quietly in the background and won't alter your text unless you trigger it. You'll know it's working when your corrections fire instantly—no splash screens, no distractions.

Press Win + ` (backtick) whenever you make a double-capitalization mistake. CAps scans your entire document and corrects all double-caps errors in one go—no cursor dragging required.

Note: The backtick shares a key with the tilde, which is to the left of the number 1 key.

Yes. CAps is open-source and digitally signed. You can verify the executable using the trust guide, which includes hashes and signature instructions.

CAps won't collect data, phone home, or modify your system—it's designed for transparency and user control.

Absolutely. CAps is tested on both Windows 10 and Windows 11, and works with most applications that accept standard keyboard input.

If you run into an edge case (like a sandboxed app or elevated window), let me know—I'm always striving to improve compatibility.

Nope. CAps is a fully self-contained executable—no need to install AutoHotkey separately.

I compiled CAps using AutoHotkey's standalone compiler, which bundles the interpreter directly into the .exe. That means:

• ✅ You can run CAps on any Windows system without installing anything else
• ✅ No background dependencies, registry changes, or system-wide hooks
• ✅ Just download, run, and you're good to go

If you're curious or want to inspect the source, I do provide the original .ahk script in my GitHub repo, but it's totally optional.

It's a false positive. A few antivirus engines (typically around 5 out of 100) flag unsigned executables by default, especially when distributed outside major app stores.

CAps is completely open-source and digitally signed. You can verify its authenticity using our trust guide, which includes hashes and GPG signature instructions.

Yes. Each release includes a GPG signature (.sig) and public key (CAps_public.asc), so you can confirm that your download hasn't been tampered with.

I also include a reference hash list—see Verify_Hashes_2.1.1.txt on the verification page.

Yes. Browser warnings can appear when downloading software from personal sites or GitHub repos. They aren't based on the actual file contents.

CAps doesn't contain malware and provides multiple ways for users to verify its integrity. Check our trust guide to confirm that the download matches the expected hashes and signatures.

Because it's independent and open-source. CAps doesn't pay for app store validation, antivirus whitelisting, or Windows branding.

Instead, it's built around user trust—clean code, reproducible builds, and cryptographic verification you can do yourself.

I recommend using Kleopatra or GPG. Just import the public key, then check the accompanying .sig file for signature match.

You can also compare hash outputs manually using tools like certutil or Get-FileHash in PowerShell.

CAps is built using AutoHotkey v2, which compiles scripts into 32-bit executables by default—even on 64-bit systems. This doesn't affect performance or compatibility. CAps runs smoothly on both 32-bit and 64-bit Windows environments, and its integrity is verified regardless of architecture.

CAps is a portable, on-demand tool and only runs when launched manually, exiting cleanly when closed. It doesn't install services, background processes, or auto-start behavior. You can confirm this by checking Task Manager or using CAps's own verification guide.