Exporting Kneeboards

The primary way to share a finished kneeboard is to publish it. Publishing gives you a read-only public URL that any pilot can open without a DKS account, and for package flights it publishes every flight in the package together. The DTC button handles in-cockpit cartridge loading separately.

Top-Bar Buttons

Publish (Cloud Icon)

Publishing is the recommended way to distribute a kneeboard. The cloud icon in the top bar publishes the design to a public /view/{uuid} URL — anyone with the link can open it in read-only form with no login required. Squadron members can already see every squadron design in the app, so publishing is primarily for sharing outside the squadron.

For package flights, publishing any flight (or the master) publishes the entire package together. You don't need to publish each flight individually — every pilot in every flight in the package goes live at once.

Once a design is published the cloud button swaps to an "Open Published" action so you can jump straight to the live URL. Unpublishing lives in the right-click context menu under Share & Export → Unpublish Design.

DTC Export (In-Game Cartridge)

The DTC button downloads a Data Transfer Cartridge file you can load in DCS via the in-game DTC feature. DTC export is supported for:

• F-16C Viper
• F/A-18C Hornet
• AH-64D Apache
• OH-58D Kiowa
• C-130J Hercules

Each aircraft has its own DTC payload with the fields that aircraft's DTC system understands (waypoints, radios, and aircraft-specific data). The exact contents evolve over time as DCS's DTC parsers change, so refer to DCS's own DTC documentation for the authoritative list of what loads where.

For the F-16C and F/A-18C, the cartridge also carries the battlefield graphics you draw on the map (GEO lines on the Viper; FLOT, FAOR, and corridor lines on the Hornet's SA page). Which graphic lands on which page depends on its Kind — see Battlefield Graphics → Sending graphics to the in-game DTC for the full mapping.

Squadron administrators can set DTC defaults that apply automatically to every export — see Squadron Settings.

Per-Pilot Personalization

When you publish a package or design, each pilot in the flight gets their own personalized view. What varies per pilot:

• Callsign and aircraft number come from the Flight Members tab.
• Loadouts can be shared across the flight or configured per-pilot (see the Loadout tab).
• DTC fields are personalized when exporting DTC cartridges (laser codes and similar).

Shared across all pilots: waypoints, comm plan, OPFOR, bullseye, support assets, and everything else that isn't pilot-specific.

Publishing is disabled until at least one flight member has a tactical callsign filled in on the Flight Members tab — without a callsign there's no pilot to personalize for.

Export to JSON

For backups or transferring a design to another account, right-click → Share & Export → Export to JSON dumps the full form data for the design.