Who mouzi is for#
Developers downloading packages, docs, and build artifacts
Developers accumulate a mix of zip archives, installers, PDFs, and screenshots throughout a typical workday. mouzi automatically routes each type to its own subfolder using extension rules, keeping the flat directory clear. The {year}/{month} path template builds a date-organized archive without manual work.
Skip if:
If you prefer a headless, scripted approach without a GUI tray app, a shell script with inotify on Linux or a PowerShell file watcher on Windows is a lighter fit.
IT administrators managing shared or lab machines
Administrators on shared Windows machines can configure mouzi to move potentially dangerous executable downloads out of the Downloads folder before less-technical users open them. The .mouziignore patterns and folder modes let you tune behavior per machine, and the portable version leaves no registry trace.
Skip if:
If you need centralized policy management across many machines simultaneously, mouzi has no management console or group policy integration. A scripted endpoint management approach suits that scale better.
Privacy-conscious users avoiding cloud file sync
Users who decline cloud file sync services for privacy or compliance reasons can get automatic folder organization entirely offline. mouzi never asks for an account, sends no telemetry, and stores everything in a local SQLite database. The full source code is publicly auditable on GitHub under the MIT license.
Skip if:
If your threat model requires avoiding any tray application with file system write access, mouzi's features require that permission. A manual sorting workflow would better satisfy a stricter posture.
Users sorting Google Takeout archives after leaving Google Drive
Users who stop using Google Drive desktop sync often need a way to re-sort the archive they exported. mouzi can import Google Takeout .zip, .tgz, or .tar.gz archives, extract them to a staging folder, and apply your existing rules to sort the contents automatically, without manually unzipping and reorganizing.
Skip if:
If you need the sorted files synced across devices as well, mouzi handles only the local-sort side. You would need a separate local sync tool alongside it.
The problem it solves#
Downloads folders accumulate faster than most people sort them. A week of active work means PDFs from documentation sites, zip archives from GitHub releases, executable installers, screenshots, and exported spreadsheets all landing in the same flat directory. Finding a specific file means scrolling past dozens of unrelated ones, and the manual habit of creating subfolders rarely survives a busy schedule.
The challenge compounds for IT administrators managing shared machines or power users with strict folder conventions. A download from the wrong application lands in the wrong place, and tracking it down consumes time that was never budgeted. Privacy-sensitive users face an additional pain: cloud-based file sync tools that offer auto-organization typically require account creation and may cache file metadata on remote servers outside the user's control.
How it solves it#
Rule-based file sorting
Define rules by file extension, regex pattern, name prefix, file size, or modification date. Rules run top-to-bottom; the first match wins, so you can place a catch-all at the bottom for files that do not match anything specific. Paths support dynamic placeholders like {year} and {month} for date-organized folder hierarchies.
Organization preview before moving
Before mouzi moves a batch of files, you can review the matched rules and destination paths in a preview screen and approve or reject individual operations. Added in version 0.2.0, this prevents misfiled items when testing a new rule or processing an unusual batch of downloads.
History and verified undo
Every file move is logged to a local SQLite database with the source path, destination, rule applied, and timestamp. You can search history by filename, extension, or date range and undo individual moves or entire organization runs. mouzi skips files that have since been modified or whose source paths are now occupied.
No cloud, no telemetry, no account
File names, paths, and contents never leave your device. There is no registration step, no telemetry sent, and no cloud sync component. Configuration and history live in a local SQLite database you can inspect, move, or delete at any time. Releases are built from tagged commits in public GitHub Actions workflows, so the build pipeline is auditable.
.mouziignore pattern support
Per-folder ignore patterns work like .gitignore: add a .mouziignore file or configure patterns in Settings to skip browser temporary files, OS metadata files like Thumbs.db and .DS_Store, or any filename pattern that should stay in place. Wildcards, exact names, and folder patterns are all supported.
Three folder modes for any workflow
Each watched folder runs in silent mode (move files as they arrive), manual mode (queue files until you click Organize Now), or paused mode (watch without moving anything). Version 0.2.0 also added suggest mode, which flags files for review rather than moving them automatically, giving you a preview-first workflow for folders with mixed or sensitive content.
Strengths and trade-offs#
Strengths
- MIT license with no recurring costmouzi is MIT-licensed and free to download, install, and run with no subscription and no per-feature paywall. File Juggler and File Arbor are paid products in the same category; mouzi removes that cost entirely. The MIT license also allows modification, forking, and redistribution without restriction.
- Fully offline with auditable buildsEvery organization rule runs on the local CPU against the local disk. Nothing is sent to a server. Releases are compiled in public GitHub Actions workflows from tagged commits, so any user can verify the binary matches the source. Code signing with the SignPath Foundation is in progress for Windows releases.
- Minimal resource footprintmouzi uses approximately 5 MB of RAM while running in the background. The Windows NSIS installer is around 4.8 MB. The tray icon adds negligible CPU overhead outside active organization runs, making it unobtrusive on constrained machines or workstations already running many background services.
- Active development with parallel platform releasesThe project launched in May 2026 and reached version 0.2.1 in September 2026. Within four months it shipped automatic update checks, Google Takeout archive import, a preview-and-approve mode, history filters, and verified undo. Both Windows and Linux receive parallel releases with each version.
Trade-offs
- -Windows releases currently lack code signingAs of version 0.2.1, Windows builds do not yet carry Authenticode signatures. The project has applied to the SignPath Foundation and the approval is in progress, but current Windows releases will trigger a SmartScreen warning on download. Users can verify files using the SHA-256 checksums published in each GitHub release.
- -Single-maintainer project at version 0.2.xmouzi is maintained by one developer working after hours. The project launched in May 2026 and is at version 0.2.1 as of September 2026. Feature requests, bug fixes, and platform support depend on a single contributor's availability. There is no enterprise support tier, no paid SLA, and no guaranteed issue response time.
- -No macOS support yetmouzi runs on Windows 10/11 and Linux only. macOS support is listed in the project roadmap as a future goal but has no committed release date. Users who primarily work on macOS cannot use mouzi until that port ships.
mouzi vs alternatives#
mouzi vs File Juggler
File Juggler and mouzi both use rule-based automation to sort files into destination folders as they arrive in watched directories. File Juggler is a paid Windows application; mouzi is MIT-licensed, free, and runs on both Windows 10/11 and Linux.
| Feature | mouzi | File Juggler |
|---|---|---|
| License | MIT (free) | Proprietary (paid) |
| Platforms | Windows 10/11, Linux | Windows |
| Source code | Public on GitHub | Closed |
| Cloud required | No | No |
mouzi is the stronger fit when you need Linux support alongside Windows, want zero license cost, or want to inspect and verify the code running on your file system. The MIT license permits modification and redistribution without restriction.
File Juggler is a commercial product with a longer track record. It suits teams that need formal customer support or prefer a commercially maintained application over a project at version 0.2.x with a single maintainer.
mouzi vs File Arbor
File Arbor is a paid file organization tool in the same category as mouzi. Both products apply rule-based sorting to incoming files in watched folders.
| Feature | mouzi | File Arbor |
|---|---|---|
| License | MIT (free) | Proprietary (paid) |
| Platforms | Windows 10/11, Linux | Windows |
| Source code | Public on GitHub | Closed |
| Privacy | Local-only, no telemetry | Not documented |
mouzi covers the same core automation at no cost, adds Linux support, and operates without any network component. For privacy-focused users or regulated environments, the auditable build pipeline and local-only architecture are concrete differentiators.
File Arbor suits users who require a commercial support relationship, formal release documentation under an SLA, or a vendor relationship for procurement compliance.
Quick start#
Install from source using Rust (latest stable) and Node.js 22+.
```bash
git clone https://github.com/hsr88/mouzi.git
cd mouzi
npm install
npm run tauri dev
```What it's built on#
- Languages
- JavaScriptRustTypeScript
- Frameworks
- React
FAQ#
Does mouzi work on macOS?
No. mouzi 0.2.1 supports Windows 10/11 and Linux only. macOS support appears in the project roadmap as a future goal but has no committed release date. Users on macOS will need a different file organizer until that port ships.
Is mouzi free to use?
Yes. mouzi is MIT-licensed and free to download and run on Windows and Linux with no subscription, no account creation, and no feature limits. The developer accepts optional support via Ko-fi and GitHub Sponsors, but payment is never required.
How does mouzi handle partial downloads and browser temp files?
mouzi checks for file locks before any automatic move and skips files that browsers are still writing. A configurable grace period adds a short delay before processing new files, giving incomplete downloads time to finish. Browser temporary files matching known patterns are excluded by default.
Can I build mouzi from source?
Yes. The full source is on GitHub under the MIT license. You need Rust (latest stable) and Node.js 22 or later. Clone the repository, run npm install, then run npm run tauri dev to start a hot-reloading build on Windows or Linux.
Where does mouzi store its rules and history?
Rules, history, and configuration are stored in a local SQLite database in your user profile folder. The database file is separate from the application itself; you can inspect it with any SQLite viewer, move it, or delete it at any time. Uninstalling mouzi does not automatically remove the database.
Similar open-source tools#
mvt
Mobile forensics toolkit for detecting spyware on Android and iOS
supervision
Python toolkit for computer vision detection, tracking, and annotation
BrewUI
Homebrew's official macOS GUI for package management
OpenFlux
TCP tunneling via Yandex Docs or WebRTC transports
Sonarr
Smart PVR for Usenet and BitTorrent TV fans
iloader
Free open-source iOS sideloader for Windows, Mac, and Linux