Zush Templates: Reusable AI File Renaming Workflows
Jump to section
Quick answer: Zush Templates let you save a reusable rename setup for a specific workflow. Instead of rebuilding the same pattern for screenshots, expenses, audio tracks, legal files, or client notes, you choose the template and apply it to the next batch or monitored folder.
Templates matter because file naming is not one-size-fits-all. A music export should not be named like a tax receipt. A client call should not be named like a design screenshot. The best filename depends on the folder.
What a template can standardize
A useful template can capture:
- filename structure
- date format
- AI naming instructions
- Naming Blocks
- metadata and tag preferences
- monitored folder behavior
That means a template can turn repeat work into one click.
For field-level control inside templates, see Naming Blocks: Build Searchable File Names from 145+ Fields. For choosing the AI processing mode behind a template, compare Cloud AI vs Local AI File Renaming.
Built-in workflows where templates help
Templates are useful for recurring folders such as:
- screenshots and UI references
- expenses, receipts, and invoices
- music tracks, loops, and stems
- client meeting notes and call recordings
- legal files and signed agreements
- travel bookings and confirmations
- watched folders that receive new files every day
Template examples
| Workflow | Template pattern |
|---|---|
| Client calls | {client_name}_{meeting_topic}_{date} |
| Music loops | {artist}_{title}_{bpm} |
| Invoices | {vendor}_{invoice_number}_{date} |
| Screenshots | {app}_{screen}_{task} |
| Legal files | {counterparty}_{document_type}_{date} |
Three worked templates
A pattern on its own is only half a template. These three show the whole setup — blocks, formatting, and where the template gets applied — for workflows that recur often enough to be worth saving.
1. Screenshot capture folder
Problem: the screenshot folder fills with Screenshot 2026-05-16 at 10.02.11.png, and nothing in that name says which app or which bug.
Template:
- Naming Blocks:
{date}then{app}then{title} - Formatting: lower case, hyphen separator, ISO date
- Applied to: a monitored folder pointed at wherever macOS or Windows drops screenshots
Result: 2026-05-16-figma-checkout-mobile-wireframe.png, 2026-05-16-stripe-monthly-revenue-chart.png.
Date first keeps the folder in capture order; the app block is what makes a later search for “stripe” work at all. Two content blocks are enough here — screenshots are usually looked up by “when and what app”, not by a long description.
2. Expenses and receipts
Problem: receipts arrive from email, downloads, and a scanner, all named by whatever system produced them, and at tax time none of them are findable.
Template:
- Naming Blocks:
{date}then{vendor}then{amount} - Formatting: ISO date, lower case, hyphen separator
- Applied to: a batch run over the year’s receipt folder, then the same template attached to the folder for new arrivals
Result: 2026-04-30-aws-412-80-usd.pdf, 2026-03-11-apple-store-89-00-usd.pdf.
Sorting by name now sorts by month, and every vendor total is visible without opening a single file. Review this one in the preview before applying — vendor and amount are read out of the document, and a low-quality scan is where they go wrong.
3. Client deliverables
Problem: three clients, overlapping project names, and files called v2 FINAL final.psd.
Template:
- Naming Blocks:
{client_name}then{project}then{document_type}then{title} - Formatting: lower case, underscore between sections
- Applied to: each client’s working folder, per batch at handoff time
Result: acme_site-rebuild_statement-of-work.pdf, acme_site-rebuild_hero-banner-dark.psd.
Client comes first because that is how the folder is actually browsed. The date is deliberately absent — for deliverables the version and document type matter more than the day, and the file system already tracks modification dates.
For field-by-field detail on the blocks used above, see Naming Blocks or the Templates docs.
Why templates pair well with folder monitoring
Folder monitoring is strongest when new files arrive in predictable places. A Downloads folder might need general naming, while a Podcast folder needs guest and topic context. Templates let each monitored folder keep its own rules.
That gives you automation without flattening every file into the same generic naming style.
If you are evaluating tools before building templates, start with AI renamer tools comparison.
FAQ
Are Templates a PRO feature?
No. Templates are included in the free version of Zush, along with Naming Blocks and custom AI prompts, so you can build repeatable naming setups before upgrading.
Can one template handle mixed file types?
Yes. A client project template can handle PDFs, docs, screenshots, audio, and videos while still using file-specific Naming Blocks when they are available.
