Unforgotten

Why I Keep Coming Back to Unforgotten

Unforgotten is not the most polished thing out there, but it gets the job done if you know what you are doing. I have been using it for about three years now, mostly for tracking and organizing asset pipelines in game production. The interface looks like it was built in 2012, and honestly, it still feels that way. But the underlying logic is solid, and it handles edge cases better than most of the alternatives I have tried. Most people install it and immediately get confused by the project structure. You do not just open it and start typing. There is a specific way you set up your workspace, and if you skip that step, you will spend the next two hours fighting with import errors. I learned this the hard way on a tight deadline for a mid-budget indie project. We missed our sprint goal by half a day because nobody bothered to read the setup documentation. Just follow the workflow I describe below and you will save yourself that headache.

Getting Started with Unforgotten

First, grab the latest release from the official channel. The file size is around 340MB, which is reasonable. Do not download random mirrors you find on forum threads. People have reported corrupted builds from third-party hosts. Once you have the installer, run it as administrator on Windows, or use sudo on Linux. The program writes to system-level directories and you will get permission errors otherwise. After installation, launch it and you will see a blank workspace. This is normal. Click File then New Project. You will be asked to choose a pipeline type. Select Custom if you are doing general asset management, or pick one of the presets if your project matches a standard format. Naming your project matters later. Do not use spaces or special characters. I once named a project "Boss Battle v2 (final)" and spent forty-five minutes debugging broken file paths because the parser choked on the parentheses and spaces. From there, you need to map your source directories. This is where most beginners stall out. Go to Settings, then Data Sources. Add your project folders one by one. Each folder needs a unique alias and a category tag. The category tag determines how Unforgotten processes files in that folder. Use descriptive tags like "textures," "scripts," "models" rather than vague ones like "assets" or "stuff." I cannot stress this enough. Your future self will thank you.

Core Workflow in Practice

The main value of Unforgotten is its deduplication engine. When you scan directories, it compares files by checksum and metadata to find duplicates, orphaned references, and version conflicts. This alone is worth the installation time. A typical full-scan of a medium-sized project with about 12,000 files takes roughly eight to twelve minutes on a modern SSD. On an HDD it can stretch to twenty minutes or more. Plan accordingly. Once the scan completes, you get a results dashboard. The interface shows you four main categories: Duplicates, Orphans, Conflicts, and Stale References. Click on any category to see the details. The Duplicate view is particularly useful. It groups files with matching content but different names or locations. You can select groups and choose to consolidate them, which moves everything into a single canonical location and updates all internal references automatically. This saves hours of manual cleanup work. Here is a specific edge case that cost me a full workday. I had a project where several texture files were stored in nested subfolders with slightly different resolutions but identical content. Unforgotten flagged them as duplicates, which was correct. But the conflict resolution script broke when it encountered a file path longer than 260 characters on Windows. The error was silent, meaning the tool reported success but actually did not update the registry entries for those files. The workaround was simple but not obvious. I had to enable the "Short Path Mode" option under Advanced Settings, which uses a different parsing algorithm that handles long paths correctly. It is not mentioned prominently anywhere in the docs. I only found it by reading through the source code comments on the GitHub issue tracker.

Common Pitfalls to Avoid

Unforgotten does not handle incremental scans the way you might expect. If you modify a single file in your project and rerun a full scan, the tool recomputes everything from scratch rather than comparing against a cached state. This means every scan is a full sweep. For large projects this becomes a real bottleneck. The current workaround is to use the Watch Folder feature, which monitors specific directories in real time and only processes changes. Set this up before you start your project, not after. Configuring it mid-project caused data inconsistency issues for me that took an afternoon to resolve. Another thing that catches people off guard is the export function. Unforgotten can generate reports in CSV, JSON, and its own proprietary .ufg format. The CSV output looks clean but omits metadata fields like creation timestamps and creator information unless you explicitly enable the "Include Extended Fields" option. I wasted a morning wondering why my audit report was missing half the columns I needed. It was a checkbox setting I had never noticed. The software also struggles with certain file types. It handles common formats like PNG, JPG, FBX, and GLB well. But custom binary formats, especially those used by proprietary game engines, often produce parse errors or incomplete data. If your project relies heavily on custom formats, you may need to write a small plugin or converter. There is a plugin API, but the documentation is sparse. The community has shared a few examples on the forums, which helped me get a basic converter working, but expect to invest some time there if you need it.

When Unforgotten Is Not the Right Tool

I should be honest about the limitations. If you are managing fewer than 500 files, this tool is overkill. You would be better off using something simpler like a spreadsheet or a lightweight folder organization tool. The setup overhead is not worth it for small-scale work. If you need real-time collaboration with a team, Unforgotten does not support concurrent editing of the same project database. It is designed for single-user workflows. Multiple users can read from the same directory, but conflicts will arise if two people write changes simultaneously. For teams that need collaborative asset tracking, you might be better served by a dedicated DAM system like ShotGrid or even a properly configured Perforce setup. Those tools cost money and have steeper learning curves, but they handle multi-user scenarios correctly. Unforgotten fills a gap for solo developers or small teams who need something lightweight and free. It is not a replacement for enterprise-grade solutions.

Final Notes

The developer updates the software roughly quarterly. Recent patches have improved stability significantly, but you will still encounter occasional crashes when scanning deeply nested directory structures with thousands of symbolic links. If that happens to you, try disabling symlink following in the settings. It slows the scan down a bit but prevents the crash. Also, make regular backups of your Unforgotten project files. The program itself is stable, but corrupt project databases do happen, usually after an unexpected shutdown or power loss. There is no auto-recovery mechanism beyond the last manual save. If you decide to give it a shot, start small. Run it on a single folder first, get comfortable with the interface, then expand your scope. The tool rewards patience and careful setup. Rush through the configuration and you will pay for it later. Done right, it cuts what would otherwise be a tedious manual audit process down to something manageable in an afternoon.