File extension, lock, Finder label and legacy codes

These actions change the Finder-level attributes of files and folders. They are quick to apply to hundreds of items, which is the point: the Finder’s Get Info window does the same things one file at a time.

Change the visibility of the file extension

Tick Hide File Extension to hide the extension in the Finder, untick it to show it. This is the per-file setting from the Finder’s Get Info window, not the Finder preference that shows all extensions; the file name itself is not changed.

Change the file lock

Tick Lock file to set the lock flag, untick it to clear it. Locked files cannot be modified, renamed or moved to the Bin without confirmation, and no action in A Better Finder Attributes can change a locked file either, so this is also the way to unlock a batch before processing it.

Set the Finder label

Choose one of the colour labels or none. The classic Finder labels appear as colour tags in today’s Finder, so this action sets or clears the colour tag on every file.

Legacy creator and type codes

Classic Mac OS identified a file’s type and the application that created it with two four-character codes. Modern macOS relies on the file extension, but some older applications and workflows still read the codes, and a wrong creator code can make a document open in the wrong application.

• Set the legacy file creator and type codes: enter the Creator Code and Type Code, or click Same As… to take both from a file that opens correctly. Add… and Delete… manage a list of saved combinations.
• Set the legacy file creator code and Set the legacy file type code change one of the two.
• Remove creator and/or type code: choose Remove creator and type, Remove only creator or Remove only type. Removing the creator code hands the file back to the system default application for its extension.

Making the Finder notice

The Finder caches file information and sometimes keeps showing the old label or lock state. The Force Finder update after operation is complete setting takes care of this; see forcing a Finder update.