> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/export-and-print-a-design.md).

# Export & Print a Design

## **Export a circuit page in WMF or DXF graphics formats** <a href="#saving-a-circuit-page-in-wmf-or-dxf-graphics-formats" id="saving-a-circuit-page-in-wmf-or-dxf-graphics-formats"></a>

HYPERSIM can export diagrams in standard **WMF (Windows Metafile)** and **DXF (AutoCAD)** graphics formats. This feature enables you to transfer graphical representations of your schematics to other applications for plotting, editing, or inclusion in documentation.

* **WMF** is a standard Windows format used to represent graphical objects such as lines, circles, and text. It is widely supported by Windows-based graphics and word processing applications.\
  HYPERSIM can generate WMF files but cannot import them. A WMF file contains only graphical information and does not include data related to signal connectivity, pin functions, attributes, or other schematic properties.
* **DXF** is a format developed by Autodesk for use with AutoCAD and other CAD tools. It is supported by most general-purpose drafting applications.

{% hint style="info" %}
Like WMF, a DXF file provides only a graphical representation of a diagram and does not include the information required to reconstruct a logical schematic. HYPERSIM cannot import DXF files. Additionally, enhanced metafiles and bitmap images embedded in a diagram (such as logos in a title block) are not included when exporting to DXF..
{% endhint %}

### **Generate a WMF file** <a href="#generating-a-wmf-file" id="generating-a-wmf-file"></a>

1. Open the design file you wish to export. If your design has multiple pages and you only want to export one of them, make that the current page (i.e. the topmost window).
2. Select the **Export** command in the **Options > Export > Export** menu.
3. Select the **WMF** option and click **Next**
4. Select either **Export all Pages** or **Export Current Page Only**, as appropriate.
5. If desired, click the **Browse** button to enter a different filename. The default will be the same name as the design with the extension changed to **WMF**.
6. Click the **Finish** button to complete the operation.

### **Generate a DXF file** <a href="#generating-a-dxf-file" id="generating-a-dxf-file"></a>

1. Open the design file you wish to export. If your design has multiple pages and you only want to export one of them, make that the current page (i.e. the topmost window).
2. Select the **Export** command in the **Options > Export > Export** menu.
3. Select the **DXF** option and click **Next**
4. Select the appropriate color option. If you choose the **Export Color Information** option, HYPERSIM will choose the closest standard DXF color for each object on the schematic.
5. Choose whether you want to use Release 12 or Release 13 format. Release 13 provides better representation of curves and ellipses, but is not compatible with all readers. You should try a test run with the desired target application (making sure your test includes a variety of symbols) before doing any major conversions.
6. Click the **Next** button.
7. Select either **Export all Pages** or **Export Current Page Only**, as appropriate.
8. If desired, click the **Browse** button to enter a different filename. The default will be the same name as the design with the extension changed to **WMF**.
9. Click the **Finish** button to complete the operation.

{% hint style="info" %}
For some applications, advanced editing capabilities can be achieved by simply copying and pasting an HYPERSIM circuit into the target application window.
{% endhint %}

## **Print a design** <a href="#closing-a-design" id="closing-a-design"></a>

Use **File > Print** to print all or part of a circuit diagram to any available printer or output device.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-81677e1033615c15bb7fa84fc9db016abb260478%2Fprint-dialog-box.png?alt=media" alt="" width="289"><figcaption></figcaption></figure>

A "sheet" refers to the **printable/visual canvas properties** of a page within a design. It defines how a page looks and prints. When printing, page numbers refer to **printed sheets**, not schematic pages. **Printed sheets** are numbered sequentially from the top-left corner of the first page to the bottom-right corner of the last page.

{% hint style="info" %}
Printed page numbers are not displayed unless they are explicitly added using **text variables**.
{% endhint %}

Use **File > Print Setup** to configure the paper size and orientation. These settings are saved with the design and determine:

* The page boundaries used for printing.
* The displayed page breaks (if enabled).
* The appearance of page borders in the schematic, depending on the sheet size settings.

### Print h**ierarchical designs**

In the **Printing** tab of the **Design Preferences** dialog box, configure the scope of the **Print** command for hierarchical designs.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fc3be5c313dd46a5a1bb7754e9ba745bfc4bad91%2Fdesign-preferences-print.png?alt=media" alt="" width="497"><figcaption></figcaption></figure>

| Parameter                                             | Description                                                                                                                                                              |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Print current circuit level only**                  | Print command prints only pages belonging to the circuit level in the current window.                                                                                    |
| **Print all unrestricted circuits in current design** | Design's master circuit and all unlocked internal circuits are printed. The locked setting is controlled by a check box in the Properties command for the parent device. |
| **Print all circuits in current design**              | Print the design's master circuit and all internal circuits, regardless of locked status.                                                                                |

When printing a hierarchical design, the master circuit is printed first, followed by each hierarchical subcircuit and its contents. Printing proceeds recursively through each level of the hierarchy.

For example, given the hierarchy shown below, the print order would be:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-220cb6922dac63a65a0a8daa573be1eea7ecad81%2Fdesign-hierarchie.png?alt=media" alt=""><figcaption></figcaption></figure>

The print order of hierarchical subcircuits within the same parent circuit is determined by HYPERSIM's internal storage order and cannot be specified by the user. As a result, circuits at the same hierarchy level (such as **W** and **X**) may be printed in a different order.

When printing a hierarchical design, the **$PRINTPAGENUMBER** text variable can be used to [display sequential page numbers](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-and-manage-designs/display-attributes-and-variables-on-the-schematic.md) on the printed output.

This variable is evaluated only during printing. When displayed in the schematic editor, it behaves like **$PAGENUMBER**, showing the page number within the current circuit.


---

# 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://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/export-and-print-a-design.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.
