An AI-generated filename is useful when it identifies the file, preserves the details needed to distinguish it and avoids unsupported information. In our eight-file Zush pilot, some names captured useful identifiers, while one contract title left out details we would need in a larger archive.
I build Zush. This was our own small application check, run on September 5, 2026, on macOS 26.5.2 with Apple Silicon. It was not an independent review or a representative accuracy benchmark.
What we ran
The set contained three text PDFs, an image-only receipt PDF, two text-based PNGs, a synthetic spoken WAV and an existing Zush demo MP4. The documents used fictional content.
Zush 3.11.0 (165) ran with Cloud AI and the existing Smart Title Name template. Its configured output language was Russian. We applied eight suggestions to isolated copies; SHA-256 checks confirmed that all eight files retained their original contents.
The table below contains all eight Zush outputs from the saved test record. This account evaluates those results without ranking products.
Where the names helped
For file_001.pdf, Zush applied Счет NS-1042 От Northstar Studio.pdf. In English, that means an invoice from Northstar Studio with the identifier NS-1042. It captured two useful retrieval fields: vendor and invoice number. The recorded name did not include the date.
For the image-only receipt, file_004.pdf became Чек Pine Street Cafe.pdf. The cafe name came through in the result even though the PDF had no selectable text and carried the generic metadata title "Benchmark fixture." We recorded the resulting name, not the internal processing steps.
The WAV became Обсуждение Осеннего Запуска Продукта.wav, describing a discussion of an autumn product launch. The MP4 became Демонстрация Работы Приложения AI Rename.mp4, describing an AI Rename application demonstration. These English explanations are translations for the reader; the Cyrillic strings are the recorded filenames.
Where a correct title was still incomplete
The service agreement became Соглашение Об Оказании Услуг.pdf, meaning "Service Agreement." That identifies the document type, but leaves out the parties and draft status.
In a folder containing a single agreement, it may be enough. In a client archive with twenty agreements, it is unlikely to distinguish the one you need. To evaluate the name, first decide which agreement someone needs to find.
For this file, a future test could require the parties and draft status explicitly, then check whether the configured workflow supplies them correctly. We did not run that test here.
What this pilot does not establish
Eight applied names are not an accuracy percentage. This was one pass with a small controlled set. It did not test Windows, local models, large files, naming collisions, repeated-run consistency or undo. Backend model IDs were not exposed in the observed UI.
Custom AI Blocks were not tested either. Zush documents configurable naming fields, but that capability should not be presented as a result of this run.
The content-hash check has a similarly narrow meaning: file bytes stayed unchanged for these eight applied renames. It does not establish how every downstream project would respond to changed paths.
How to make the next check more useful
Before running another batch, define the required fields for each file. Preserve the unedited proposals. Record missing fields, unsupported details, manual corrections and operational failures separately. Align templates and output languages when comparing applications.
The complete recorded Zush outputs
The following names are transcribed from the saved September 5 test record. They are the original Russian outputs, not rewritten English examples. All eight suggestions were applied to test copies.
| Input | Applied filename |
|---|---|
| file_001.pdf | Счет NS-1042 От Northstar Studio.pdf |
| file_002.pdf | Соглашение Об Оказании Услуг.pdf |
| file_003.pdf | Протокол Встречи Autumn Product Launch.pdf |
| file_004.pdf | Чек Pine Street Cafe.pdf |
| file_005.png | Чек-Лист Доступности Веб-Сайта.png |
| file_006.png | Статистика Ежемесячных Запросов В Поддержку.png |
| file_007.wav | Обсуждение Осеннего Запуска Продукта.wav |
| file_008.mp4 | Демонстрация Работы Приложения AI Rename.mp4 |
Source: Zush's local pilot record, ai-file-renamer-pilot-2026-09-05, including the saved application outputs and setup notes. The standalone evidence-file URL was unavailable when this article was prepared, so this table reports the recorded observations directly. The public Zush methodology provides general evaluation context; it is not the raw dataset for this particular run.
For the next run, I would check whether someone can find the requested file from its new name. Recording a rename for every input does not answer that question.
Top comments (0)