> For the complete documentation index, see [llms.txt](https://manual.karamba3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.karamba3d.com/beta/3-in-depth-component-reference/3.7-export/3.8.5-export-model-to-etabs-.e2k.md).

# 3.8.5 Export Model to ETABS (.e2k)

Karamba3D can export the structural model to the `.e2k` text format used by **ETABS**. After exporting, the `.e2k` file can be imported into ETABS to continue with structural analysis, code checks, or detailing workflows.

<figure><img src="/files/ASrOn55IbW3xG4btxsn2" alt=""><figcaption><p>Fig. 3.8.5.1: ETABS export component with user-defined storey definitions.</p></figcaption></figure>

### Inputs

In addition to the standard export component inputs, the **e2k Exporter** provides two additional inputs:

* **Names**\
  Specifies the names of the stories associated with the elevations defined in the **Elevations** input.
* **Elevations** (*Elev*)\
  Defines the vertical positions at which reference stories are generated.

The **Names** and **Elevations** inputs must contain the same number of elements. If the lists differ in length, the component will not accept the input.

### Overview

`.e2k` is a plain-text format that describes an ETABS model's internal data structure in a tabular, hierarchical layout, parsed strictly from top to bottom.

```shellscript
$ POINT COORDINATES
  POINT "1" 0 -2,5
  POINT "2" 0 0

$ LINE CONNECTIVITIES
  LINE  "C1"  COLUMN  "2"  "2"  1
```

ETABS references point coordinates using storey definitions. The exporter therefore relies on a valid storey layout to position all imported objects correctly.

By default, the exporter automatically generates storey definitions based on the model elements encountered during processing. This can result in an excessive number of stories being created in ETABS. To control this behaviour, the **Elevations** and **Names** inputs can be used to explicitly define the storey levels and their labels.

Generated "$ STORIES" output for provided input in Fig. 3.8.5.1:

```shellscript
$ STORIES - IN SEQUENCE FROM TOP
  STORY "Level1"  HEIGHT 5  MASTERSTORY "Yes"
  STORY "Base"  ELEV 0
```

If the user-defined storey set is incomplete (e.g. it does not cover the full vertical extent of the model), the exporter will automatically add additional stories above or below as required to ensure that the resulting ETABS model remains valid.

The exporter converts Karamba3D objects into their corresponding ETABS entities as follows:

| Karamba3D              | ETABS counterpart                                                                                                      |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Supports               | Point restraints (assigned at joints)                                                                                  |
| Linear Elements        | Frame elements, automatically classified based on orientation                                                          |
| Surface Elements       | Area elements; planar shells are imported as native surfaces, while curved (arc, Bézier, circular) edges are preserved |
| Beam Joints            | Frame end releases applied to corresponding frame elements                                                             |
| Materials              | Material definitions and properties                                                                                    |
| Spring                 | Line spring properties assigned to the host element                                                                    |
| Point loads            | Joint forces and moments                                                                                               |
| Imposed displacements  | Ground (support) displacements                                                                                         |
| Element loads          | Frame or area loads, depending on the host element type                                                                |
| Load cases             | Load patterns and load cases                                                                                           |
| Load case combinations | Load combinations                                                                                                      |

#### Limitations

* **Non-planar shells are not supported**\
  Karamba3D attempts to export shells as native ETABS area objects. For this to succeed, an underlying Brep representation must be available for the mesh (see [3.9.1 Mesh Breps](/beta/3-in-depth-component-reference/3.8-utilities/3.8.1-mesh-breps.md)). If the exporter encounters a mesh without underlying Brep or non-planar geometry, the element cannot be exported, as ETABS does not support curved surfaces.
* **Limited beam cross-sections**\
  Only I, T, Box, Trapezoid, and circular profiles are currently supported. All other cross-section types are ignored and reported with a warning.
* **Variable shell thickness**\
  Variable thickness definitions for membrane elements are not supported by ETABS.
* **Mesh loads are not exported**\
  Mesh-based loads must be converted into equivalent point loads prior to export, or applied directly within ETABS after import.
* **Vertical openings (e.g. windows)**\
  Openings in vertical shell elements are not fully supported and may not be transferred accurately.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.karamba3d.com/beta/3-in-depth-component-reference/3.7-export/3.8.5-export-model-to-etabs-.e2k.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
