Guides
DCS File Formats: .miz, DTC, CombatFlite, LotAtc
DCS World missions and cockpit data travel as files. DCS Planner opens those files in the browser, lets you edit the route and overlays, and writes them back for the Mission Editor, the jet, CombatFlite, LotAtc, or Tacview. This page names each format the planner actually imports or exports.
This page is the import and export detail for the step-by-step DCS mission planning workflow.
The .miz mission file
A .miz is the DCS World mission file. It is a ZIP archive. Inside, a Lua table named mission holds the theater, coalitions, units, trigger zones, drawings, and bullseye. Auxiliary files cover options, warehouses, and localization. Open a .miz in the Mission Editor, host it on a server, or import it here to edit the plan in the browser.
DCS Planner imports that archive and converts DCS X/Z coordinates to latitude and longitude. You can change units, drawings, and bullseye. A .miz does not fill the planner route; see DCS Flight Plan: Waypoints, Headings & Routes for which imports do.
Export writes a .miz for Saved Games\DCS\Missions. The file carries units, trigger zones, drawings, bullseye, and coalition nav points. It does not embed a DTC cartridge or kneeboard PNGs. Open the exported file in the Mission Editor, or host it.
To open a mission online:
- Open DCS Planner. Open DCS Planner in the browser. No login is required for import and export.
- Import the file. Import a .miz, .trk, or CombatFlite .cf. LotAtc .env, DCS-DTC JSON, native .DTC, and Route Tool .lua also import.
- Review theater and contents. Confirm the theater, then pick units, drawings, and bullseye. A CombatFlite .cf can also load its route into the planner.
- Edit on the map. Move waypoints, place threats, and set bullseye. The planner stores coordinates as decimal degrees.
- Export the format you need. Write a .miz for the Mission Editor, a CombatFlite .cf, a kneeboard PNG, a DTC, LotAtc .env, Route Tool .lua, or a Tacview overlay. Copy text formats to the clipboard when you need to paste.
DTC and DCS-DTC JSON
A Data Transfer Cartridge is cockpit data, not the mission. Native .DTC export is F-16C, F/A-18C, M-2000C, and F-14B(U) only. For the F-16C and F/A-18C, put the file in Saved Games\DCS\DTC, then LOAD it from the jet DTC page. The M-2000C cartridge (route only) goes in Saved Games\DCS\Datacartridges and loads from the Mirage MIP cartridge slot. F-14B(U): Open it in the DTC window of your F-14B(U) group, then load flight plan 2 on the CDNU. The F-16C, F/A-18C, and F-14B(U) cartridges are JSON; the M-2000C cartridge is Lua. Import accepts .dtc, .json, and .lua.
What the native file holds depends on the jet. The F-16C can carry NAV steerpoints (including GEO, threat, and destination points), COMM presets, CMDS, IFF/ROE, and MFD colors. You pick those parts on the DTC page. The F/A-18C cartridge is a different dialect; see DCS F/A-18C Mission Planning & Waypoints.
DCS-DTC JSON is for the separate DCS-DTC Windows app: Load/Save, File, Load from file, then upload once you are in the jet. That JSON holds waypoints and COMM presets. It does not carry CMDS, IFF/ROE, MFD colors, or F-16 GEO / threat / destination points. See the DCS F-16 DTC Guide (Data Transfer Cartridge) for how the Viper cartridge is planned and loaded.
A Route Tool .lua is another jet-side file: steerpoints only, for Saved Games\DCS\Config\RouteToolPresets. It is not a DTC.
CombatFlite .cf
CombatFlite is a desktop DCS planner. Its .cf file is a ZIP that embeds a full DCS mission plus a CombatFlite mission.xml (routes, packages, airspaces, bullseyes).
DCS Planner imports .cf: it parses the embedded mission like a .miz, then enriches the plan with CombatFlite routes and packages from mission.xml. Export writes a .cf CombatFlite can open with File, Open. The export carries steerpoints, units, trigger zones, drawings, bullseye, and coalition nav points.
Use .cf when you share a plan with someone who works in CombatFlite. Use .miz when the next stop is the Mission Editor or a DCS server. Moving off CombatFlite? See what a .cf import keeps in DCS Planner.
LotAtc .env
LotAtc is the radar client GCI and AWACS controllers use on a DCS server. An .env file is a drawing layer for that scope, stored as JSON in lat/lon.
DCS Planner imports .env drawings onto the map and exports drawings, trigger zones, and steerpoints as a LotAtc layer. In the LotAtc client, open Draw and use Load/Save. A server admin who wants the layer at start renames it .json and puts it in Saved Games\DCS\Mods\services\LotAtc\userdb\drawings\blue (or red).
LotAtc .env does not carry SAM or AAA units. Place those in a .miz. Draw circles or polygons when the controller needs rings on the scope. See DCS SAM Threat Rings & Route Planning for how those overlays relate to threat rings.
The planner also exports a Tacview overlay XML (drawings and zones as static objects) into %APPDATA%\Tacview\Data\Static Objects. Tacview import is not supported.
.trk tracks and PNG kneeboards
A .trk is a DCS track: the mission plus replay data from a flown sortie. DCS Planner imports .trk the same way as .miz. It reads the embedded mission (units, drawings, bullseye) and ignores the replay. There is no .trk export.
A kneeboard is a stack of PNG pages you flip in the cockpit. DCS Planner writes those images from the current plan: an 800 by 1200 Spider card page around bullseye (1600 by 2400 pixels), and 768 by 1024 Mission pages (1536 by 2048 pixels). Copy them into Saved Games\DCS\Kneeboard. The planner does not export a PDF and does not embed those PNGs in a .miz. See Custom Kneeboard Pages in DCS for where DCS loads the pages and how a .miz carries its own.
Which format for which job
Pick the file by who reads it next. Text formats (DCS-DTC JSON, Route Tool Lua, LotAtc .env, Tacview XML) can also copy to the clipboard.
| Format | Import | Export | Carries | Used for |
|---|---|---|---|---|
| .miz | Yes | Yes | Units, trigger zones, drawings, bullseye, coalition nav points | DCS Mission Editor and multiplayer host |
| .trk | Yes | No | The embedded mission (same fields as a .miz). Replay data is ignored | Open a flown track as a mission in the planner |
| CombatFlite .cf | Yes | Yes | Steerpoints plus an embedded .miz (units, zones, drawings, bullseye) | Round-trip with CombatFlite |
| LotAtc .env | Yes | Yes | Export: drawings, trigger zones, and steerpoints as a drawing layer. Import: drawings only. Not SAM units | LotAtc GCI/AWACS scope overlays |
| Native .DTC | Yes | Yes (F-16C, F/A-18C, M-2000C, F-14B(U)) | Steerpoints, radios, and jet-specific partitions on the DTC page | LOAD in the cockpit DTC page |
| DCS-DTC JSON | Yes | Yes | Waypoints and COMM presets. Not CMDS, IFF/ROE, or MFD colors | DCS-DTC Windows app |
| Route Tool .lua | Yes | Yes | Steerpoints only | DCS Route Tool presets |
| Tacview overlay .xml | No | Yes | Drawings and trigger zones as static objects | Tacview debrief overlay |
| Kneeboard PNG | No | Yes | Spider card and Mission pages as images. Not a mission file | In-cockpit kneeboard (Saved Games\DCS\Kneeboard) |
FAQ
- What is a .miz file in DCS?
- A .miz is a DCS World mission: a ZIP archive whose mission Lua table holds units, trigger zones, drawings, and bullseye. Open it in the Mission Editor, host it on a server, or import it into DCS Planner to edit the plan in the browser.
- Can I open a .miz file online?
- Yes. DCS Planner imports .miz (and .trk) in the browser. You review theater, units, drawings, and bullseye, edit them on the map, then export a new .miz or another format. The planner does not run the mission.
- What is the difference between a .miz and a DTC?
- A .miz is the world: units, drawings, and bullseye for the Mission Editor. A DTC is cockpit data for one jet (steerpoints and radios). DCS Planner exports them as separate files. The .miz export does not embed the cartridge.
- Does DCS Planner import CombatFlite .cf files?
- Yes. A .cf is a ZIP with an embedded DCS mission plus CombatFlite mission.xml. Import loads the mission and enriches it with CombatFlite routes, packages, and airspaces. Export writes a .cf CombatFlite can open.
- What is a LotAtc .env file?
- It is a drawing layer for the LotAtc radar client. DCS Planner exports .env with drawings, trigger zones, and steerpoints. Import brings the layer back as drawings only. It does not carry SAM or AAA units. Load it from LotAtc Draw, Load/Save.
- Does DCS Planner export a kneeboard PDF?
- No. Kneeboard export is PNG only: an 800 by 1200 Spider card page (1600 by 2400 pixels) and 768 by 1024 Mission pages (1536 by 2048 pixels). Copy those files into Saved Games\DCS\Kneeboard. The planner does not write PDF and does not embed the PNGs in a .miz.