FilesOrganization

Bulk rename and reorganize image files

Rename image files based on content, metadata, or a consistent naming pattern.

Last tested Mar 2, 2026

Access Scope

Local Folders

Images folder

Permitted Actions

read
write
rename
delete

Workflow Steps

undefined

Scan images read-only first

undefined

Define naming convention

undefined

Preview proposed names

undefined

Review and confirm

undefined

Execute the renames

Cowork Prompt Pack

Cowork-ready
List all image files in [folder] with names and sizes. Read-only, no renaming.
Works best when you limit Cowork to specific folders and verify before destructive actions.

Verification Checklist

0 of 4 verified

Why consistent image naming matters

Random filenames like "IMG_20260910_123456" or "Screenshot 47" make images hard to find, organize, and understand. When you need a specific photo later, searching for "IMG_" across 500 files is tedious. A consistent naming convention like "2026-09-10_project-name_001" tells you the date, project, and sequence instantly.

This workflow is especially valuable for:

  • • Photographers organizing shoots by date and event
  • • Teams maintaining consistent asset libraries
  • • Archivists creating structured image collections
  • • Marketing departments organizing campaign assets by date and type
  • • Anyone who inherits hundreds of poorly-named photos

Naming patterns to consider

Common patterns:

  • YYYY-MM-DD_description_001 — Date-based, useful for chronological organization
  • ProjectName_SubjectArea_001 — Project-based, groups related images
  • Event_Date_Location_001 — Event-based, captures context
  • Client_DeliverableType_Draft-01 — Client-based, tracks version status

The key is consistency: pick one pattern and stick with it across all images in a folder.

Step-by-step best practices

1. Always preview first

Claude generates a side-by-side preview showing original names → new names. Review this carefully before approving. Look for naming conflicts, typos, or unexpected changes.

2. Keep originals as backup

Renaming is reversible but tedious. Consider keeping a copy of the folder before bulk renaming, or ask Claude to generate a manifest you can use to revert if needed.

3. Handle duplicates explicitly

If two images would get the same name, Claude should append sequential numbers (001, 002, etc.). Confirm this behavior before executing.

4. Test on a small batch first

Rename 10-20 images, verify the results, then expand to the full folder. This catches naming issues early.

Common questions

Can Cowork rename based on image content?

Not directly from file content, but you can describe what's in images: "These are product photos. Name them by product type: Product_OfficeChair_001, Product_Desk_001, etc." Cowork will apply the pattern consistently.

What if I mess up the naming pattern?

The safest approach is to keep a backup folder, rename in the copy, and verify results before applying to originals. Or ask Cowork to reverse the naming by showing you the reverse mapping.

Can I exclude certain files?

Yes. Tell Cowork explicitly: "Rename all .jpg and .png files but skip .psd and .tiff files" or "Skip any file starting with 'FINAL_'."

Related workflows and resources

Excel to PowerPoint

Analyze data and generate slides

Folder Organization Pack

Structure and categorize files

Organize Downloads

Sort and organize a downloads folder

All Workflows

Browse other file and organization workflows
← Back to all workflows