> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/commands-overview/publish/export-step.md).

# Export STEP

## Command Description

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2Ff8sMLcthdnUWi1xSr1X9%2Fimage.png?alt=media&amp;token=cff07b7a-f524-4b31-9c41-2cf7e7683193" alt=""><figcaption></figcaption></figure>

This command exports a 3D model to a STEP file. The export can be manual or automatic on the save event. The command can be configured in the Be.Smart T4I Settings window on the Publisher -> STEP tab.

## Command Location

* Part and Assembly environments

## Command Settings

`Be.Smart T4I -> Be.Smart T4I -> Edit settings -> Publisher -> STEP`

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2F9iAhTBVLBfW5maUkoFl4%2Fimage.png?alt=media&amp;token=8f0a23d8-1b71-409b-8053-3cdc4b998f5e" alt=""><figcaption></figcaption></figure>

1. Automatically creates STEP file from active part or assembly after saving.
2. Set output folder for STEP files. When empty, STEP is created in the STEP subfolder in the same location as the source part or assembly. More can be found in [Saving files using relative paths](/t4i/commands-overview/be.smart-t4i/edit-settings/publisher/saving-files-using-relative-paths.md).
3. Select the application protocol (the purpose and amount of internally stored information) for the exported STEP file.

{% hint style="warning" %}
For larger files, the publishing process may take a long time to complete. In such cases, it is not recommended to use automatic on-save publishing. To speed up your workflows, disable the on-save publishing in settings and use manual publishing instead.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.besmart.software/t4i/commands-overview/publish/export-step.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.