LinuxWhat is the MIF file format?
.mif files are associated with MapInfo software, originally developed by MapInfo Corporation - now owned by Precisely (acquired from Pitney Bowes in 2020).
Files with a .mif extension store geographical vector data in plain text (ASCII) format. Each .mif file is structured in two sections: a header and a data section. The header carries declarations such as Version, Charset, Delimiter, and CoordSys (projection), while the data section holds geometry primitives - Point, Line, Pline, Region, Arc, Text, and more. Because .mif is entirely human-readable ASCII, the file can be inspected or edited in any plain-text editor. .mif files are commonly used by various GIS software for data exchange.
GIS stands for Geographic Information System - any software for collecting, storing, analyzing, or visualizing geographical data. GIS applications can be divided into two groups, commercial and free open-source tools, and many different GIS data formats are in use. .mif is widely supported because it is an open, documented interchange format rather than an opaque binary.
.mif files always travel with a companion .mid file that shares the same base name. The .mid file holds the attribute (tabular) data for each geometry object defined in the .mif - one row per feature, in matching order. This pairing is not optional: geometry without attributes or attributes without geometry is incomplete. Together, the .mif/.mid pair forms MapInfo's documented, vendor-neutral exchange format - distinct from MapInfo's proprietary binary .tab working format.
Because .mif/.mid is open and well-specified, tools such as QGIS, GDAL/OGR (ogr2ogr), and ArcGIS can read and write the format directly. For modern interchange, formats such as GeoJSON are increasingly common, but .mif remains widely encountered in legacy datasets and long-running GIS workflows.
Security & safety
RISK: LOWMIF and MID are plain-text data files with no executable content, so they are safe to open. The real pitfalls are practical, not malicious: a .mif is useless without its matching .mid (you lose all attribute values), the two must stay in sync line-for-line, and an incorrect or missing CoordSys clause will place the data in the wrong location until you set the right projection on import. Edit them only with GIS tools or a careful text editor, since hand-edits easily break the geometry/attribute correspondence.
Format details
in a nutshell- Adobe FrameMaker Maker Interchange Format - A text-based document interchange format used by Adobe FrameMaker (.mif) - unrelated to GIS; common in technical-documentation workflows.
- ImageMagick MIFF (Magick Image File Format) - ImageMagick's native raster image format (usually .miff, sometimes .mif) - the name carried in this DB entry, but a different format from MapInfo.
Programs that open MIF files
Windows3 apps
MapInfo Pro
Paid Table > Open Universal Data (or Import) and choose the MIF/MID pair to load it as a MapInfo table. 
QGIS
Open-source Layer > Add Layer > Add Vector Layer, select the .mif (the .mid is read automatically); reproject or export as needed.
GDAL/OGR (ogr2ogr)
Open-source Run ogr2ogr -f "ESRI Shapefile" out.shp input.mif to read and convert MIF/MID from the command line. 
macOS1 app
Technical details
deep spec| File structure | Two-section plain-text file: a header block of declarations followed by a `Data` section containing geometry primitives, one per feature |
| Header version clause | First line of every `.mif` file is `Version <n>` (e.g. `Version 300`, `Version 900`), identifying the MIF generation used |
| Character encoding | Plain ASCII text; the active encoding is declared by a `Charset` clause in the header (e.g. `WindowsLatin1`, `UTF-8`) |
| Coordinate system | `CoordSys` clause in the header defines the map projection and datum; the CRS is preserved when the file is imported or exported |
| Geometry types | `Point`, `Line`, `Pline` (polyline), `Region` (polygon), `Arc`, `Ellipse`, `Text`, `MultiPoint`, `Collection` |
| Attribute storage | Attribute data lives in a companion `.mid` file - comma- or tab-delimited text, one row per geometry feature in the `.mif` |
| Field delimiter | Configurable via the `Delimiter` header clause; defaults to the tab character if omitted |
| Row-order dependency | Geometry rows in `.mif` and attribute rows in `.mid` are matched strictly by line order; there is no cross-file ID reference |
| MIME type | `application/x-mapinfo-mif`; also commonly served as `text/plain` |
| File signature | No binary magic number; file begins with the ASCII string `Version` followed by a version integer on the first line |
| Compression | None - the format is uncompressed plain text by design |
| Typical file size | A few KB for small datasets up to hundreds of MB for large vector layers; size scales linearly with feature count and coordinate precision |
| Application support | MapInfo Pro (native read/write), QGIS, GDAL/OGR (`ogr2ogr`), ArcGIS (via Data Interoperability extension) |
| Developer lineage | Created by MapInfo Corporation; acquired by Pitney Bowes; now maintained by Precisely (acquisition completed 2020) |
| Relation to native format | Open, documented interchange counterpart to MapInfo's proprietary binary `.tab` file set; intended for cross-application data transfer |
| Released | Early 1990s, with MapInfo for Windows |
| Latest version | MIF/MID interchange version 900 (current MapInfo Pro era); format stable for decades |
| Open standard | Yes · royalty-free |
| Specification | www.precisely.com |
MIF conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about MIF files.
Frequently asked questions
How do I open a MIF file?
What is the .mid file that came with my .mif?
How do I convert MIF/MID to a Shapefile?
ogr2ogr -f "ESRI Shapefile" out.shp input.mif. Geometry, attributes and projection are preserved.
