Can Zush rename RAW photos?

Yes. Zush supports common RAW formats including CR2, CR3, NEF, ARW, DNG, ORF, RAF, RW2, PEF, SRW, SR2, and RAW. It analyzes available previews and metadata, proposes a new filename, and preserves the file extension.

Can AI rename video clips by what is in them?

Yes. Zush samples frames and uses available subtitle or transcript context when present, then proposes a descriptive name for supported formats such as MP4, MOV, M4V, MTS, M2TS, and others. Review the batch before applying it.

Can it name clips by scene, location, or take?

Yes. Add those fields to a Template or describe a studio-specific field with a Custom AI Block. Results depend on the visual and metadata context available in each file, so the preview step is important for ambiguous clips.

Does Zush replace a photo catalog, editor, or NLE?

No. Zush handles the filename layer around your existing workflow. It renames media in ordinary folders before import, during handoff, or in an archive; it does not replace culling, color, editing, catalogs, timelines, or digital asset management.

Does renaming change photo metadata or video content?

No. Zush changes the filename and path, not image pixels, video content, or embedded metadata, and supported RAW files keep their extension. Catalogs, timelines, RAW+JPEG pairs, and XMP sidecars can maintain their own links, so test a copied folder and rename before import unless you have verified relinking in the destination application.

Can I keep unreleased or private client work offline?

Yes. Local AI uses Ollama models for supported analysis on Mac or Windows, so file content is not sent to Zush or a third-party AI provider. It works offline after setup. You can also use BYOK when your studio routes analysis through its own provider account.

Can I undo a renamed shoot?

Yes. Review all proposed filenames before applying them, and use rename history to revert a batch if the naming rule needs another pass.

Does Zush move or upload my photo and video files?

Zush renames files in place and does not move them into a new library or store them. Cloud processing can send a compact analysis payload; BYOK uses your provider account; Local AI keeps supported analysis on the machine.

Rated by4.5 Rated on5.0

For photographers and videographers

AI file renaming for photographers: organize shoots by project, scene, and take

Zush is a desktop AI file renamer for photographers and videographers. It combines available metadata with visual content to name RAW photos, JPEGs, and supported video clips, while your catalog, editor, or NLE remains the creative system.

Download for Mac

Download for Windows

RAW, photo, and video formats
Custom naming Templates
Preview and undo every batch

Built for visual workflows

From card ingest to client delivery, keep every filename useful

Use the same naming layer across stills, footage, exports, and archives without replacing the creative tools your team already knows.

Portrait, wedding, and event photographers
Replace repeated camera counters with project, date, subject, moment, and location — useful before culling and still understandable years later.
Videographers and editors
Turn generic camera clips into searchable b-roll, interview, location, scene, and take names before the edit begins.
Studios and production teams
Give assistants, producers, and editors one shared convention for ingest folders, active projects, deliverables, and archives.

Build filenames from the details your studio searches

Zush combines visible content, available metadata, sampled video frames, and your own instructions. Your Template decides which fields appear and in what order.

Choose a field to see it in the filename

DSC_4831.NEF2026-06-14 – Ortega Wedding – Ceremony

Your Template controls the order and separators. Add a Custom AI Block when your studio needs a field that is not built in.

Choose how each client shoot is analyzed

Start with managed AI, connect the provider account your studio controls, or run supported visual analysis locally for private and unreleased work.

Start quickly with Cloud AI

Fastest setup

Use Zush-managed AI to analyze visual previews and sampled video frames, then review the proposed names before applying them to the shoot.

Use your own AI account

BYOK

Connect the provider and model your studio already uses. Your API key stays in secure local storage while you control the provider account.

Keep client work on the machine

Local AI

Run supported visual analysis with local Ollama models on Mac or Windows when unreleased campaigns, private events, or client footage should stay local.

Zush renames media in place and does not become a new asset library. Choose the processing mode for each workflow, keep your existing folder structure, and use rename history when a batch needs to be reverted. Compare the three AI modes

Batch rename a shoot without rebuilding your workflow

Keep your catalog, editor, NLE, and storage layout. Add one reusable Zush naming step around the folders where media already lands.

Build the studio naming rule
Combine date, client, project, subject, location, scene, shot type, take, camera, and any custom field your team needs in one reusable Template.
Run it on an ingest or archive folder
Add a copied shoot, a card ingest, an export folder, or a mixed archive of RAW photos, JPEGs, and video clips without moving the source media.
Review, apply, and reuse
Read the proposed names as one batch, correct exceptions, apply with undo available, then reuse the same Template on the next job.

Explore AI photo renaming Explore AI video renaming Build a reusable naming Template

Why Zush

Why photographers and videographers use Zush for file naming

Zush combines visual context with dates, camera metadata, sequence fields, and studio rules to create portable filenames before import, during handoff, or in an archive.

Media file need	How Zush handles it	Workflow benefit
Describe what each file shows	Zush can propose subject, scene, location, shot type, take, and custom visual fields.	A folder becomes searchable before anyone opens every photo or clip.
Combine AI with stable metadata	Build a Zush Template from capture date, EXIF, camera, sequence, project, and AI-detected context.	Filenames stay predictable while still describing the individual shot.
Keep one convention across cameras	Apply the same field order, separator, date format, and studio rules to a mixed batch.	Files from different bodies, cards, and operators follow one naming system.
Review before import or handoff	See every original and proposed filename side by side before applying the batch.	Ambiguous subjects, scenes, and takes can be corrected before they enter production.
Recover an applied rename	Zush keeps the original-to-new mapping in Rename History.	The complete batch can be inspected and reverted when the Template needs another pass.

What a rename changes — and what to verify

Zush changes the filename and path, not the image pixels, video content, or embedded metadata.
Supported RAW files keep their original extension, and every proposed old-to-new name is visible before the batch is applied.
Rename History records the original filename, new filename, folder, and timestamp so an applied batch can be reverted.
Catalogs, timelines, RAW+JPEG pairs, and XMP sidecars can create linked workflows. Test a copied folder and rename before import unless you have verified relinking in the destination application.

Works with cloud folders

iCloud Drive
Google Drive
Dropbox
OneDrive
Box

One naming workflow for stills, footage, and deliverables

Use separate Templates for capture media and exports, or apply one studio convention across a mixed project folder.

RAW photo shoots

Turn camera counters into names that carry the project, date, subject, scene, or location while preserving the original RAW extension.

2026-06-14 – Ortega Wedding – Ceremony – First Kiss.nef

Portraits and event galleries

Apply one readable convention across JPEG, HEIC, TIFF, and RAW selects before culling, delivery, or long-term archiving.

Maya Chen – Studio Portrait – Look 02.cr3

B-roll and location footage

Name short clips by visible subject, setting, shot type, and project so editors can find useful footage before opening every file.

River House – Exterior – Golden Hour – Wide.mov

Interviews and multi-camera takes

Use speaker, interview topic, camera, and take fields to make a day of similarly numbered clips easier to scan in Finder or File Explorer.

Founder Interview – Camera A – Take 04.mp4

Social and client exports

Replace final-final filenames with the project, deliverable, aspect ratio, language, or version fields your handoff requires.

Northwind Launch – Social Cut – 9x16 – v03.mp4

Mixed studio archives

Run one batch across photos, footage, audio, subtitles, and production documents, with a filename proposed from each file’s available context.

Coastal Editorial – Behind the Scenes – Studio Setup.jpg

Reusable filename recipes for professional shoots

Start with stable metadata such as date, client, camera, and sequence. Add AI-detected subject, scene, location, or shot type only where it makes the archive easier to search.

Client shoot with camera sequence

Use a deterministic date and project prefix, then retain a camera or sequence field so files from multiple bodies stay unique.

{YYYYMMDD}_{Client}_{Shoot}_{Camera}_{Sequence}

Video production and multi-camera takes

Combine project context with visible scene details, shot type, take, and camera before the clips enter an editing timeline.

{Project}_{Scene}_{ShotType}_{Take}_{Camera}

Searchable portrait or event archive

Put stable client and date fields first, then add the subject, location, or moment that distinguishes each image.

{Client}_{CaptureDate}_{Subject}_{Location}

What better media filenames change

The payoff is not cosmetic. It is media that stays understandable before import, during collaboration, and after delivery.

Find the shot before opening it

A descriptive subject, scene, location, or take turns the folder listing into a useful first-pass index of the shoot.

Keep the convention across every camera

A reusable Template makes files from different bodies, cards, and operators follow the same studio naming order.

Hand off media that explains itself

Editors and clients receive filenames that retain project context outside your catalog, NLE, shared drive, or delivery platform.

Choose your PRO plan

Monthly flexibility or one-time lifetime access. Both plans remove the rename limit across every AI mode.

Trusted by 1,500+ users

PRO Monthly

Flexible monthly plan

$10/month +VAT

Unlimited AI Renames

PRO One-Time

Pay once for lifetime access

~~$48~~$36one-time +VAT

Limited Offer25% offwith code

Unlimited AI Renames

14-day money-back guarantee • Secure via Paddle

Photo and video file renaming, answered

How Zush handles RAW photos, video clips, Templates, processing modes, batch review, existing creative tools, and undo.

A practical starting point is capture date, client or project, subject or scene, and a short differentiator such as location, shot type, or select status. Keep the order consistent and use the fields your team will actually search later.

Photo and video organization guides

Naming and archive workflows for RAW shoots, photo libraries, client exports, and video clips.

Mac Guide

Try Zush on one copied shoot folder

Start with a small set of RAW photos or clips, review the proposed names, refine the Template, and undo the batch if it needs another pass.