Open-source project
vladelaina/Catime avatar
vladelaina/Catime

Catime is a 995KB pure C Windows timer controlled from one tray icon

💌A tiny (995KB) but mighty timer in **pure C** ! — almost no memory usage!❤️‍🔥 Supports clock, countdown, stopwatch, Pomodoro, and fully customizable tray animations (GIFs, CPU/Mem%) 💘 Don't be shy, join here🧸: https://discord.com/invite/W3tW2gtp6g

4,985 stars210 forksCApache-2.0

At a glance

What is it?
A single tray icon covers clock, countdown, stopwatch and Pomodoro, and the same slot can show an animated GIF or live CPU and battery readings. The build story is Windows first: MinGW, CMake, and a Linux host used only to cross compile.
Who is it for?
Catime fits a Windows desktop where someone wants a visible timer and nothing else, and it does not fit a Linux workstation or a multi user machine without reading further than the README gets you. Before installing, pick one channel (Store, winget, Scoop or a release archive) rather than two, decide whether an animated or a system status tray icon suits a taskbar you share, and check whether the font you plan to subset contains anything beyond digits, colon and period.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 30 days ago.
What is it written in?
Mainly C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • vladelaina/Catime4,985 ★ · +131
Star history
Repository2026-09-232026-11-14
vladelaina/Catime4.9k5k

131 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Left-click sets the time, right-click opens the menu, edit mode does the rest

The tray icon is the main control surface, which decides how much you can reach from it. Left-clicking the tray icon sets the time. Right-clicking sets the menu, and the menu is where the modes live: the project covers clock, countdown, stopwatch and Pomodoro inside a 995KB executable written in pure C. Position and size are handled in a separate edit mode rather than in the menu. In that mode you drag to move the window, use the scroll wheel to resize, hold Ctrl while scrolling to adjust opacity, and right-click again to leave edit mode. That is the whole documented gesture set, and it is short enough to learn in one sitting. The cost is for keyboard first users: none of the documented interactions is a shortcut, even though the project description does advertise shortcuts, so any key binding has to come from the user guide at vladelaina.github.io/Catime/guide rather than from the README.

config.ini sits under %LOCALAPPDATA%, so state follows the user, not the folder

Settings live in a single INI file at a fixed path:

text
%LOCALAPPDATA%\Catime\config.ini

That location has consequences worth knowing before you install. Because the file sits under LOCALAPPDATA rather than beside the executable, copying the program folder to another machine or another Windows account gives you default settings instead of your own. The README does not document pointing Catime at a different config path or running it without writing state, so anyone planning a shared kiosk, a locked down lab image or a second Windows account should confirm the behavior in the user guide first rather than assume per installation settings exist.

Store, winget, Scoop and the release archive are four doors with no stated upgrade path between them

There are four ways in. GitHub Releases is the direct route, and the recent tags are v1.6.2 from 2026-08-27, v1.6.0 from 2026-08-23 and v1.5.0 from 2026-07-09. Scoop takes two commands, because the package lives in the extras bucket:

bash
scoop bucket add extras
scoop install catime

Winget takes one:

bash
winget install --id VladElaina.Catime

A Microsoft Store listing sits in the badges under apps.microsoft.com/detail/9n3mzdf1z34v. No channel is described as tracking the others, so a machine that mixes a Store install with a Scoop install has two installers writing into the same config path and nothing on record about which copy wins. Pick one door and stay in it.

MinGW and CMake are the documented toolchain, and the Windows steps are spelled out one by one

Source builds need MinGW and CMake, and Windows is treated as the real target. The required tools table names MinGW as the GCC compiler with a specific archive pattern, x86_64-<version>-release-win32-seh-ucrt-rtv<num>-rev<num>.7z from the niXman mingw-builds-binaries releases, and CMake as cmake-<version>-windows-x86_64.msi from cmake.org. The Windows steps are explicit: extract MinGW to C:\mingw64, add C:\mingw64\bin to Path under System variables through the Environment Variables dialog, and install CMake with the Add CMake to the system PATH option selected. Verification is two commands:

bash
gcc --version
cmake --version

Then the build runs build.bat on Windows or build.sh elsewhere:

bash
chmod +x build.sh && ./build.sh   # Linux
build.bat                         # Windows

A mingw-w64-toolchain.cmake file at the top level, next to CMakeLists.txt, shows the cross compile setup is part of the build rather than something you configure by hand.

The apt and pacman lines build a Windows binary from a Linux host

The dependency block in the getting started section is where expectations get reset:

bash
git clone https://github.com/vladelaina/Catime.git
cd Catime

# INSTALL DEPENDENCIES
# Ubuntu/Debian
sudo apt update && sudo apt install -y mingw-w64 cmake

# Arch Linux
sudo pacman -Syu --noconfirm mingw-w64 cmake

# Windows - See setup instructions below

That last comment is the tell. On Windows the block stops and defers to the MinGW and CMake instructions. On Linux and Arch it installs a mingw-w64 cross compiler, which pairs with the mingw-w64-toolchain.cmake file at the repository root. So the Linux side of this project is a build host, not a runtime target, and build.sh exists to produce the Windows executable. Anyone expecting a Linux timer, or a Linux package shaped like the Scoop bucket, will not find one here.

A plugin writes ./output.txt and that string becomes the tray

The plugin contract is one line long. A plugin writes its output to ./output.txt, and Catime displays it in real time. No API, socket or configuration file is described, which makes plugins writable in any language. Whatever a plugin writes is what Catime displays. Two companion repositories are recommended alongside the main one: Catime-Plugins for more plugins, and MemeTray for animation collections.

GIF, WebP, ANI, PNG and JPG fill the icon slot, and CPU, memory, battery and Caps Lock can fill it instead

What the tray can show is a short list of formats and four live readings. Custom animations accept GIF, WebP, ANI and static images such as PNG and JPG, so the icon can be an animated file instead of a static one. The same slot can be handed to system status: CPU %, memory %, battery % and Caps Lock state are all supported as real time displays, which turns the timer into a status indicator without adding another process. Underneath both modes sits a narrower constraint, because the timer draws only numbers and symbols and the character set it needs is 0-9, `:` and `.`. The official Font Simplification Tool uses exactly that to cut a custom font file by more than 90%, and the advice attached to it is to keep the original files, because a future update may need characters beyond today's set. Subset the font and you save disk space at the price of a timer that can no longer draw anything new.

The banner still says v1.5.0 while the newest tag is v1.6.2

Release hygiene is the weakest surface here. The banner at the top of the README still announces v1.5.0, while the releases page has v1.6.2 published on 2026-08-27 and v1.6.0 on 2026-08-23. The last push to the repository was on 2026-10-16, so commits continue after those tags, and the tree holds four build scripts: build.sh, build.bat, build_monitor.ps1 and build_worker.bat. Provenance is handled in the usual files: Apache-2.0 in the LICENSE file, PRIVACY.md and SECURITY.md at the top level, and Windows code signing provided by SignPath.io with the certificate from the SignPath Foundation. What is absent is any statement about which channel is canonical, so treat the release page as the source of truth for the version you actually run.

Editorial conclusion

Catime fits a Windows desktop where someone wants a visible timer and nothing else, and it does not fit a Linux workstation or a multi user machine without reading further than the README gets you. Before installing, pick one channel (Store, winget, Scoop or a release archive) rather than two, decide whether an animated or a system status tray icon suits a taskbar you share, and check whether the font you plan to subset contains anything beyond digits, colon and period.

Frequently asked questions

What does Catime do on Windows?

It is a pure C timer that lives in the system tray and covers clock, countdown, stopwatch and Pomodoro modes, with a transparent interface and tray animations in GIF, WebP, ANI, PNG and JPG. Settings are written to %LOCALAPPDATA%\Catime\config.ini.

How do I install Catime on Windows?

Three package routes are given: scoop bucket add extras followed by scoop install catime, winget install --id VladElaina.Catime, and the Microsoft Store listing under apps.microsoft.com/detail/9n3mzdf1z34v. A direct download sits on the GitHub releases page.

How do I build Catime from source?

MinGW and CMake are required. On Ubuntu or Debian run sudo apt update && sudo apt install -y mingw-w64 cmake, on Arch run sudo pacman -Syu --noconfirm mingw-w64 cmake, then build with build.bat on Windows or ./build.sh elsewhere.

Where does Catime keep its settings?

In one INI file at %LOCALAPPDATA%\Catime\config.ini. The README does not document an option to point the program at a different file, and the path follows the Windows user profile rather than the program folder.

How do Catime plugins work?

A plugin writes its output to ./output.txt and Catime displays it in real time. Two companion projects are recommended for more plugins and for animations: Catime-Plugins and MemeTray.

Can I use a smaller font file with Catime?

Yes, through the official Font Simplification Tool, which reduces a custom font file by more than 90%. Catime displays only numbers and symbols, the characters 0-9, colon and period, and the project advises keeping the original font files as backups.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. vladelaina/Catime on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/vladelaina-catime.svg)](https://hysenlabs.com/projects/vladelaina-catime)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/vladelaina-catime.svg)](https://hysenlabs.com/projects/vladelaina-catime)

Was this useful?