Smart Rename in AVE: context-aware video names without touching your original files

by

AVE could already analyze footage locally and distinguish what was happening in different clips—but the asset library could still be full of names like IMG_4821, MERT8581, or butterfly_2.

That felt wrong. If an AI video editor understands that one clip contains a red butterfly and another contains a blue butterfly, those distinctions should be reflected in how the footage is organized.

So I shipped Smart Rename in AVE.

It uses the project context and AVE’s local analysis to suggest distinct, descriptive names across a collection. Every suggestion is reviewable and editable before applying. You can exclude clips, undo the operation, and keep the names through save, reopen, and relink.

Smart Rename is available from Assets, Ask, Plan, and connected MCP assistants.

For now, it changes names inside AVE only. Original media files and AVE-managed copies remain untouched.

This leads to the next product question:

Would you want an optional “Rename original files” action—with a full preview and confirmation—or should a video editor always leave source filenames alone?

I’m leaning toward keeping AVE names separate by default and making original-file renaming an explicit optional tool. Curious what other editors and creators would expect.

12 views

Add a comment

Replies

Best

Nice feature.

I think keeping the original filenames untouched by default is the right choice. It avoids accidentally breaking existing workflows, while still giving users a much better way to organize footage inside AVE.

An optional "Rename original files" action with a clear preview sounds like the best of both worlds.

 Exactly. Also it’s lowkey dangerous to let local AI roam on the disk surface.

Optional rename original files would be cool. Users may even use AVE to organize irrelevant folders and files perhaps 🤷‍♂️

Something like ‘It’s a video editor but with perks’