After implementing feedback from r/macapps, I realized organizing files wasn't enough.
[Problem] While organizing different archives, I realized that organizing files wasn't enough. Before organizing an archive, I first needed to know whether the media itself was actually valid. That's why Version 2.0 introduces Validate Media. Instead of assuming every file is usable, MediaOrganizer now verifies media integrity before the normalization process begins. Unreadable, damaged and corrupted media are automatically separated into a review structure instead of silently becoming part of the organized archive. The comparison from my previous post still summarizes where MediaOrganizer fits among other approaches, so I decided to keep it unchanged. [Compare] There isn't really a direct competitor in this space. MediaOrganizer Studio doesn't replace Apple Photos, Lightroom or other cataloging tools. It focuses on preparing media before cataloging by combining archive validation, metadata normalization, location recovery and deterministic organization into a single workflow. [Pricing] One-time purchase : USD 29.99 App Store: https://apps.apple.com/ch/app/mediaorganizer-studio/id6755330599 [Changelog] V2.0.0 • Introduced Validate Media, a new integrity validation stage before media organization. • Reorganized the output structure into organized and review, making archive inspection easier before final use. [AI Disclaimer] Text reviewed with AI assistance. The app itself uses deterministic local processing and does not use AI/ML features. The workflow has now become: Validate Media ↓ Normalize Media ↓ Recover Location ↓ Add Location (currently in development) ↓ Organized Archive Complete workflow: https://brightfoundry.info/mediaorganizer/workflow/ Version 2.0 has just been released. I'm always interested in hearing suggestions and discussing ideas for future versions.
Collected discussion
i like that your listening to feedback and pivoting accordingly. i have a few concerns tho mainly around the AI. is the AI on device or is it external, as i have sensitive business documents i wouldn't want to send to external servers. also how do the results compare from this to say just getting Claude Cowork to sort and organise files?
Thanks! I really appreciate the feedback. One clarification: MediaOrganizer doesn't use AI at all, either on-device or in the cloud. It was intentionally designed as a fully local, deterministic media processing workflow. Your photos and videos never leave your Mac. During processing, only GPS coordinates are sent to the geocoding service to retrieve location names and administrative descriptions, which are then used during the metadata normalization process. No media files are ever uploaded. Even Recover Location, which may look AI-assisted at first, doesn't use AI either. Instead of guessing locations, it helps you recover them by using your own media as the reference source. It analyzes only the files contained in the folder you choose and lets you define the search criteria. The application simply finds media that already contain GPS metadata and uses those as deterministic references to help you assign locations to media files that don't already contain GPS metadata. MediaOrganizer was built around two core principles: privacy and local-first processing. Those principles are non-negotiable. Regarding Claude, I think they're solving different problems. Claude can help reason about files or answer questions, but MediaOrganizer performs batch validation, metadata normalization, GPS recovery, duplicate-aware organization, and archive restructuring directly on the media files themselves. It was built specifically to process large personal media archives while keeping everything local, private, and deterministic.
Validating media before organizing it sounds like a very nice feature. One of those things where I hadn’t thought about it, but after hearing it, it makes complete sense
That was exactly my reaction during this project. The turning point came the day I opened a photo and it was full of gray corruption bands. Until then, I had always assumed that if a file existed, it was still valid. That made me stop and research the most common reasons media files become unreadable or invalid. Those checks eventually became the first step of my workflow, because it made much more sense to validate everything before organizing it. Once damaged or unreadable files become part of an organized archive, finding them later becomes much harder. I documented the reasoning behind that workflow here if you're interested: https://brightfoundry.info/mediaorganizer/workflow/
Validation before normalization is a strong boundary because it prevents cleanup from hiding damage. The next UX layer I would want is provenance and repairability: a machine-readable manifest with the original path, checksum, exact reason code, and action taken for every file. “Unsupported codec” should be visibly different from “corrupt,” since those imply very different recovery paths. Quarantine should be reversible, and a rerun should skip known-good files without changing their metadata again. A preflight summary showing readable, unsupported, suspicious, and damaged counts would also make the operation easier to trust before it touches a large library. If the process stops halfway, resuming from the manifest is safer than rediscovering state. For a utility like this, confidence comes less from the happy path than from being able to explain and undo every decision.
Thanks! I really appreciate the detailed feedback. Some of the concepts you mentioned are actually already part of the current design. Validation doesn't just create a single "invalid" folder. MediaOrganizer classifies media by the exact technical reason and preserves that information both in the folder structure and in the validation log. For example: review/ invalid/ images/ unreadable_image/ visually_damaged_image/ zero_bytes/ videos/ unreadable_video/ video_frame_decode_failed/ zero_bytes/ Each processed file is also recorded in the validation log using explicit reason codes, followed by a summary with the totals for every category. The goal was to keep the primary output understandable by any user, while still making the log simple enough to be parsed by scripts if someone wants to perform further analysis. One important design decision is that MediaOrganizer never assumes every file placed in the invalid folders is permanently unusable. Those files are separated for manual review because some media may still be usable even though they match one of the validation rules. The application highlights potential problems, but the final decision always remains with the user. I particularly liked your suggestion about a machine-readable manifest. If advanced integration or resumable workflows become a future requirement, exporting the same information as structured data (JSON/CSV/SQLite) could be a natural evolution. Thanks again for taking the time to share these ideas!