Resource fork

A resource fork is a <a href="/facts/Fork_(file_system)/B1QFYk2t">fork</a> of a <a href="/facts/Computer_file/FjFH3Ufm">file</a> on <a href="/facts/Apple_Inc./oTJYta3k">Apple</a>'s <a href="/facts/Classic_Mac_OS/I5fQq44K">classic Mac OS</a> <a href="/facts/Operating_system/8XTuvMh2">operating system</a> that is used to store structured data. It is one of the two forks of a file, along with the data fork, which stores data that the operating system treats as unstructured. Resource fork capability has been carried over to the modern <a href="/facts/MacOS/Y93vVpTm">macOS</a> for compatibility.
A resource fork stores information in a specific form, containing details such as icon bitmaps, the shapes of windows, definitions of menus and their contents, and application code (<a href="/facts/Machine_code/bgdQ1Fxf">machine code</a>). For example, a word processing file might store its text in the data fork, while storing any embedded images in the same file's resource fork. The resource fork is used mostly by <a href="/facts/Executable/VSst9eLA">executables</a>, but any file can have a resource fork.
In a 1986 technical note, Apple strongly recommended that developers do not put general data into the resource fork of a file. According to Apple, there are parts of the system software that rely on resource forks having only valid Resource Manager information in them.
The resource fork was conceived and implemented by Apple programmer <a href="/facts/Bruce_Horn/euNht8CD">Bruce Horn</a>.

Resource fork open-in-new

Resource fork