Why convert FETCHMIRROR to PLIST?
A .fetchmirror file is a property-list document that Fetch uses to remember a Mirror window's settings. Since .plist is the very format it is stored in, the two are the same thing under different extensions, which is why no real conversion takes place.
How to convert FETCHMIRROR to PLIST
Rename the extension EASIEST
Make a copy and rename sync.fetchmirror to sync.plist. macOS then treats it as a property list you can inspect, with no data change.
Open in Xcode FREE
Open the file in Xcode's property-list editor to view the mirror keys and values; save-as a .plist if you want the explicit extension.
plutil -convert xml1 FREE
If the plist is in binary form, run plutil -convert xml1 -o sync.plist sync.fetchmirror to write a readable XML property list without altering the data model.
About these formats
A .fetchmirror file is a saved settings document from Fetch, the macOS FTP client made by Fetch Softworks. It records the configuration of a Mirror window, including the local and remote…
Open .FETCHMIRROR details →
.PLIST
Apple Property List
A .plist (property list) file stores settings and configuration data for macOS and iOS apps as key/value pairs. It comes in two forms - human-readable XML or a compact binary encoding that…
Open .PLIST details →Quality & what to watch
- The file is already a plist, so renaming or re-saving does not change its structure.
- A
.plistcopy will no longer open in Fetch as a mirror unless renamed back to.fetchmirror. - Editing keys by hand can corrupt the mirror settings if the expected structure is broken.
Frequently asked questions
Isn't .fetchmirror already a plist?
.plist version is the same file with a different extension.How do I open it as a plist?
.plist and open it in Xcode, or run plutil to view it as XML.Is it binary or XML plist?
plutil -convert xml1 turns a binary property list into readable XML.Can Fetch still use it after renaming?
.fetchmirror; Fetch matches its own extension.
