Declaring New Uniform Type Identifiers
Mac apps can add new uniform type identifiers for proprietary data formats. You declare new UTIs in the information property list (
info.plist) file of a bundle. You can declare new UTIs in any of the following:
Spotlight Importer bundles
Automator action bundles
In addition to declaring the UTI string, the declaration can contain any of the following properties:
The type’s tag specification, specifying all the alternate identifier tags that match this type
A list of UTIs to which this identifier conforms
The icon to use when displaying items of this type
A user-readable string describing this identifier, which the containing bundle may localize
Your UTI declarations must be either imported or exported:
An exported UTI declaration means that the type is available for use by all other parties. For example, an application that uses a proprietary document format should declare it as an exported UTI.
An imported UTI declaration is used to declare a type that the bundle does not own, but would like to see available on the system. For example, say a video-editing program creates files using a proprietary format whose UTI is declared in its application bundle. If you are writing an application or plugin that can read such files, you must make sure that the system knows about the proprietary UTI, even if the actual video-editing application is not available. To do so, your application should redeclare the UTI in its own bundle but mark it as an imported declaration.
If both imported and exported declarations for a UTI exist, the exported declaration takes precedence over imported one.
Here is a sample declaration for the
public.jpeg UTI, defined as an exported type, as you would find in a property list:
Table 3-1 shows a list of the available property key lists that you use in UTI declarations.
array of dictionaries
An array of exported UTI declarations (that is, identifiers owned by the bundle’s publisher).
array of dictionaries
An array of imported UTI declarations (that is, identifiers owned by another company or organization).
The UTI for the declared type. This key is required for UTI declarations.
A dictionary defining one or more equivalent type identifiers.
array of strings
The UTIs to which this identifier conforms.
The name of the bundle icon resource to associate with this UTI.
A user-visible description of this type. You can localize this string by including it in an
The URL of a reference document describing this type.
Recommendations for Declaring new Uniform Type Identifiers
If your application uses proprietary data formats, you should declare them in the
Info.plist file of your application bundle. Follow these guidelines for best results:
Your UTI string must be unique. Following the reverse-DNS format beginning with
com.companyName is a simple way to ensure uniqueness. While the system can support different UTI strings with the same specification, the reverse is not true.
If your code relies on third-party UTI types that may not be present on the system, you should declare those UTIs as imported types in your bundle.
Be sure to add conformance information if your proprietary type is a subtype of one or more existing types. In most cases you should not specify conformance to a nonpublic type, unless you are also declaring that type in your bundle. Although a custom UTI can conform to any UTI,
com.apple.packagemust be at the root of the conformance hierarchy for all custom UTIs that are file formats (such as documents); otherwise, the system can’t tell if an item on disk has that UTI. For a list of public and Apple-defined UTIs, see System-Declared Uniform Type Identifiers .