Editing Creator code (section)

{{original research|date=January 2019}}
[[Image:Mac OS window with four different MP3 files.png|frame|right|The creator code is responsible for linking the file and the program that will launch when the file is double-clicked. This Mac OS window show four files of the same [[type code]] ({{mono|MP3}}), but with four different creator codes: {{mono|Audn}} ([[Audion (software)|Audion]]), {{mono|hook}} ([[iTunes]]), {{mono|SCPL}} ([[SoundApp]]) and {{mono|NSWa}} ([[Winamp]]).]]

A '''creator code''' is a mechanism introduced in the [[classic Mac OS]] to link a data file to the [[software|application program]] which created it. The similar [[type code]] held the file type, like "TEXT". Together, the type and creator indicated what application should be used to open a file, similar to (but richer than) the [[file extension]]s in other operating systems.

Creator codes are four-byte [[OSType]]s. They allow applications to launch and open a file whenever any of their associated files is double-clicked. Creator codes could be any four-byte value, but were usually chosen so that their [[ASCII]] representation formed a word or acronym. For example, the creator code of the [[HyperCard]] application and its associated "stacks" is represented in [[ASCII]] as {{mono|WILD}}, from the application's original name of WildCard.  Occasionally they represented [[inside joke]]s. For instance, the ''[[Marathon (video game)|Marathon]]'' computer game had a creator code of {{mono|26.2}} (the approximate length, in miles, of a [[marathon]]) and ''[[Marathon 2: Durandal]]'' had a creator code of {{mono|52.4}}.

The binding are stored inside the [[resource fork]] of the application as [[BNDL]] and [[fref]] resources. These resources maintained the creator code as well as the association with each [[type code]] and [[icon (computing)|icon]]. The OS collected this data from the files when they were copied between mediums, thereby building up the list of associations and icons as software was installed onto the machine. Periodically this "desktop database" would become corrupted, and had to be fixed by "rebuilding the desktop database."<ref>[http://support.apple.com/kb/HT2344?viewlocale=en_US&locale=en_US "Mac OS: Rebuilding Desktop File and icon recovery"], Apple</ref>

The key difference between extensions and Apple's system is that file type and file ownership bindings are kept distinct. This allows files to be written of the same type - TEXT say - by different applications. Although any application can open anyone else's TEXT file, by default, opening the file will open the original application that created it. With the extensions approach, this distinction is lost - all files with a .txt extension will be mapped to a single text editing application of the user's choosing. A more obvious advantage of this approach is allowing for [[double click]] launching of specialized editors for more complex but common file types, like .csv or .html. This can also represent a disadvantage as in the illustration above, where double clicking the four mp3 files would launch and play the files in four different music applications instead of queuing them in the user's preferred player application.

macOS retains creator codes, but supports extensions as well.  However, beginning with [[Mac OS X Snow Leopard]], creator codes are ignored by the operating system.  Creator codes have been internally superseded by Apple's [[Uniform Type Identifier]] scheme, which manages application and file type identification as well as type codes, creator codes and file extensions.

To avoid conflicts, Apple maintained a database of creator codes in use. Developers could fill out an online form to register their codes.<ref>{{cite book|url=https://books.google.com/books?id=p3waZFMr97IC&pg=PA287|title=Mac OSX Programming|isbn=9780735711686|last1=Sydow|first1=Dan Parks|year=2002|publisher=New Riders }}</ref> Apple reserves codes containing all lower-case ASCII characters for its own use.

Creator codes are not readily accessible for users to manipulate, although they can be viewed and changed with certain software, most notably the macOS command line tools ''GetFileInfo'' and ''SetFile'' which are installed as part of the developer tools into ''/Developer/Tools''.