CONFIG File

What are CONFIG files and how to open them

Are you having problems opening a CONFIG file or are you simply curious about its contents? We're here to explain the properties of these files and provide you with software that can open or handle your CONFIG files.

What is a CONFIG file?

CONFIG files have multiple uses, and Ami-Back Configuration is one of them. Read more about the other uses further down the page.

Ami-Back Configuration

Ami-Back Configuration files store the saved backup or scheduling settings used by Ami-Back, a backup utility for Amiga computers. Such files record which drives or directories are to be backed up or restored, which kind of backup (e.g. full, incremental, selective), any exclusions (files or paths to skip), destination devices, archival options, scheduling times, and related behavior settings. They let Ami-Back reuse a specific set of choices without having to reconfigure each backup run.

These files are created by version 2.00 of Ami-Back (Moonlighter Software) and are read by Ami-Back when loading or applying a named configuration, especially when starting backups or restores. They are edited through Ami-Back's configuration interface; users can set up multiple configurations and schedule backups to run at specified days, times, or intervals. Besides the live execution, configuration files are preserved so that scheduled or user-initiated tasks reuse the stored settings.

Inside an Ami-Back Configuration file the very first bytes encode a signature: at offset 0 the ASCII string "AMIBACK200" identifies version 2.00 of this format.

How to open CONFIG files

Important: Different programs may use files with the CONFIG file extension for different purposes, so unless you are sure which format your CONFIG file is, you may need to try a few different programs.

While we have not verified the apps ourselves yet, our users have suggested ten different CONFIG openers which you will find listed below.

Last updated: September 2, 2026

All known file formats using extension .CONFIG

While Ami-Back Configuration is a popular type of CONFIG-file, we know of 9 different uses of the .CONFIG file extension. Different software may use files with the same extension for different types of data.

AmiDock Configuration File

The AmiDock Configuration File is used by AmiDock, a graphical dock (launch bar) in the AmigaOS Workbench desktop environment, to store all user-customizable settings for docks, subdocks, their icons, layouts, appearance, and behavior. It enables configuration of multiple docks with categories, icon arrangements, backgrounds, brush artwork, transparency, drag bars, and more. This file is created and updated by AmiDock itself via its Preferences dialog or related commands.

When AmiDock saves configuration, it writes this file so that it can later re-load the full dock setup exactly as the user arranged it: which docks exist, where they are placed on screen, which items (programs, drawers, dockies) they contain, how these items are grouped into categories, what brushes or background images are used, how icons are scaled, what orientation or margins are applied, and any user preferences for effects like transparency or drag-bars. Users generally do not edit it by hand; changes are made through the AmiDock settings UI or by using AmiDock's ARexx interface to modify components, then saved into this file.

The file starts with the ASCII signature DOCK at byte offset 0, which identifies it as an AmiDock internal configuration file. It also contains the keyword BRUSH, indicating embedded references to brush artwork used in the dock's display. These byte signatures help AmiDock distinguish its own configuration file from other files.

Application Configuration File

Files that contain the .config file extension are used by the Microsoft NET framework and are created during application development. A variety of NET framework applications use the CONFIG files. These files contain the configuration information about the program that they correspond to, including the settings and preferences of the specific application.

The CONFIG files are developer files storing information about the associated application. These files are normally stored in a text-based format. The file name will normally reference the associated application. For example, a filename.exe executable program would usually have associated a filename.config configuration file.

CONFIG opener for Windows

We have identified 4 CONFIG openers that are compatible with this specific type of CONFIG file.

DockPanel Configuration

DockPanel Configuration files record the layout of dockable windows in applications using the DockPanel Suite library for Windows Forms, so that the arrangement of tool windows, floating panels, hidden panes etc. can be restored. These files are written by a program that uses DockPanel Suite (for example, via its SaveAsXml method) and read back by that same library when the application restarts (via LoadFromXml).

Content is stored as an XML document including elements for overall layout properties (such as how much of the space is given to left/right/top/bottom docked areas, and which pane or document is active), nested elements listing all individual dockable content items (their IDs, whether hidden, floating or docked, etc.), and pane information describing grouping of content, layout within panes, and float windows. The PersistString attribute of each content item helps map serialized content back to the actual window or control when loading the layout. The file is auto-generated and not intended to be edited by hand.

As a technical identifier, the file begins with an XML declaration using UTF-16 encoding, and the root element is DockPanel with a FormatVersion attribute (commonly "1.0"). It includes nested XML tags such as <Contents>, <Content>, <Panes>, <Pane>, <FloatWindows>, etc., with attributes like DockState, AutoHidePortion, IsHidden, IsFloat, PersistString, ActivePane, ActiveDocumentPane, and DockLeftPortion / DockRightPortion / DockTopPortion / DockBottomPortion.

EasyBase DB Configuration

EasyBase DB Configuration files store the setup information for EasyBaseAC, an Amiga database application made by LOLOSoft, which allows users to define how their database behaves and appears. These files hold settings such as field definitions, window dimensions, sort-keys, and other metadata that describe the structure of a database rather than its actual entries.

EasyBaseAC writes and reads these configuration files when creating or loading a database. They are used at startup to reconstruct the record layout, window sizing, the ordering field (key field), and other structural configurations so that the display and editing behave as when last saved. The configuration lets EasyBaseAC skip sorting during load since records are stored in the user's chosen order.

Internally the format begins with a fixed ASCII header containing "EasyBase.configV1." at offset zero to identify the version and format. After that comes a global file header, followed by individual record headers and then field data. The global header includes values like number of fields, field size, flags, and possibly padding. Record headers are prefixed similarly so that EasyBaseAC can parse the structure one record at a time.

Foreign Language Master Configuration

Foreign Language Master Configuration files are used by Foreign Language Master, a translation and vocabulary learning program for the Amiga computer written by Denis Unger. These files store settings used by the software to control database loading, font display, and dictionary behavior. They are not documents or dictionaries themselves, but configuration files that tell the main program how to present and manage its language data.

The program that creates these configuration files is Foreign Language Master (often abbreviated FLM). It provides tools, such as a helper called FLMConv, which converts plain-text or ASCII wordlists into dictionary files; the configuration files are generated and updated by FLM when dictionaries or fonts are chosen or when the user changes preferences such as which dictionary files are active, how fonts are displayed, or how the user interface behaves. Users normally interact with this format through the FLM settings menu or via FLMConv when adding or modifying dictionary or font sources.

Files of this format begin with a distinct header: the first bytes at offset zero are F L M C 0 (ASCII "FLMC0"). Within the file, keywords or internal markers such as ".FONT", ".FLM", and ".URV" appear. These strings help identify the file as a Foreign Language Master config rather than another file using the same extension.

Gazebo Model Configuration

Gazebo Model Configuration files hold metadata that describes a simulation model used with the Gazebo robotics simulator. They are created by model authors to provide descriptive and identifying information about a model so that Gazebo can recognize, catalogue, and correctly use it in environments. These files are stored in model directories alongside the actual description of the model's structure and behavior.

A model author writes these files usually by hand or via tooling when creating a Gazebo model. Gazebo reads them when loading model databases so that it can display human-readable names, version numbers, author credits, and a summary description. The file also indicates which SDF (Simulator Description Format) or URDF file contains the full technical definition of the model. This allows model reuse, version tracking, and author acknowledgment.

Each configuration file is an XML document whose top-level tag is <model>. Inside, there are required elements including <name> (model's human-readable name), <version> (model version, not the SDF version), <sdf> (or URDF) referencing the actual file; plus <author> with child <name> and <email>, and <description> providing a summary. Dependencies on other models may be declared via optional <depend>-<model><uri> and <version> tags.

These files generally begin with the XML signature <?xml version="1.0"?> followed by a <model> element. Keywords that appear inside include "name", "version", "sdf", "author", "description", and in some cases "depend". They also contain strings like "MODEL", "NAME", "VERSION", "DESCRIPTION" and refer to SDF.

TUMMY Configuration

TUMMY Configuration files store data used by a small Amiga application called T.U.M.M.Y (created by Bernhard Lindner) for managing a database of Magic: The Gathering trading cards. It is the format in which the T.U.M.M.Y program saves its card collection data so that it can be searched, loaded, and updated.

The T.U.M.M.Y application acts as a catalog for Magic: The Gathering cards, letting users browse and locate cards by various criteria. This format is created by T.U.M.M.Y whenever the user saves or exports their tradeable card database. It is read by the same program in order to restore or update the stored collection of cards.

Internally a TUMMY Configuration file begins with an ASCII header line at the very start: "56.$VER:TUMMY Configuration file. Do not modify or rename!" followed by further contents held in the typical structure of the database. This header appears at offset zero.

Uropa2 Configuration

We know that one CONFIG format is Uropa2 Configuration. We have not yet analyzed in detail what these files contain and what they are used for. We're working on it.

Various apps that use files with this extension

These apps are known to open certain types of CONFIG files. Remember, different programs may use CONFIG files for different purposes, so you may need to try out a few of them to be able to open your specific file.

Help us help others

File.org helps thousands of users every day, and we would love to hear from you if you have additional information about CONFIG file formats, example files, or compatible programs. Please use the links below or email us at submit@file.org to discuss further.