23 catalogued formats

Settings & Configuration

Configuration files are small but sensitive. A misplaced character, duplicate key, or wrong encoding can stop an application from starting. INI and CONF files are usually plain text, PLIST can be XML or binary, and Windows registry exports use their own structured syntax. Always keep a backup before editing.

Why this format suite matters

  • A syntax error can break startup or silently change behavior.
  • Encoding and escaping rules differ between formats.
  • Secret keys and tokens should not be committed to version control.

Common formats in this suite

A sample of the catalog. Not every extension has a live converter.

All converters
FormatExtensionMIMENotes
BABELRC.babelrcapplication/octet-streamBABELRC settings file
DCONF.dconfapplication/octet-streamDCONF settings file
DEFAULTS.defaultsapplication/octet-streamDEFAULTS settings file
DESKTOP.desktopapplication/octet-streamDESKTOP settings file
DIRECTORY.directoryapplication/octet-streamDIRECTORY settings file
EDITORCONFIG.editorconfigapplication/octet-streamEDITORCONFIG settings file
ENVRC.envrcapplication/octet-streamENVRC settings file
ESLINTRC.eslintrcapplication/octet-streamESLINTRC settings file
GCONF.gconfapplication/octet-streamGCONF settings file
GITCONFIG.gitconfigapplication/octet-streamGITCONFIG settings file
GNOME.gnomeapplication/octet-streamGNOME settings file
KDE.kdeapplication/octet-streamKDE settings file
NPMRC.npmrcapplication/octet-streamNPMRC settings file
PBXPROJ.pbxprojapplication/octet-streamPBXPROJ settings file
PREFS.prefsapplication/octet-streamPREFS settings file
PRETTIERRC.prettierrcapplication/octet-streamPRETTIERRC settings file
RC.rcapplication/octet-streamRC settings file
SETTINGS.settingsapplication/octet-streamSETTINGS settings file
SLN.slnapplication/octet-streamSLN settings file
THUMBS.thumbsapplication/octet-streamTHUMBS settings file
VCXPROJ.vcxprojapplication/octet-streamVCXPROJ settings file
XCCONFIG.xcconfigapplication/octet-streamXCCONFIG settings file
XCODEPROJ.xcodeprojapplication/octet-streamXCODEPROJ settings file

Common workflows

Application setup

Edit a copy, validate the syntax, and keep the previous configuration.

Environment management

Use environment variables or secret stores for credentials instead of plain text files.

Migration

Translate keys carefully and compare the old and new behavior.

Before you convert

Start with the application that must open the result. Edit a copy, validate the syntax, and keep the previous configuration. Keep the original file until the output has been opened and checked. A format name alone does not guarantee compatibility, especially for settings & configuration data that may include references, layers, or platform-specific metadata.

  • Confirm the source file opens correctly in its original application.
  • Identify the exact format and version the destination accepts.
  • Keep the source until the converted file has been reviewed.

Frequently asked questions

Can I convert a binary plist to XML?
Yes, with a plist-aware tool. A generic text editor will not decode the binary structure.
Why did my app stop reading the config?
A syntax error, duplicate key, wrong encoding, or unsupported value type can prevent parsing.
Are configuration files safe to share?
Review them for passwords, API keys, hostnames, and personal data before sharing.
Can this site convert settings files?
Only where a supported converter exists. Treat configuration edits as code changes and keep backups.
What should I check before converting a settings & configuration file?
Confirm that the source opens in its original application, identify the format the destination requires, and keep an untouched copy. Test one representative file before processing a batch, especially when metadata, links, geometry, or layout matters.

Related suites and tools