> 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/create-and-manage-designs.md).

# Create & Manage Designs

## Create a new design

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-50fbaedb51a5e2f8dabc4f6d3fcea63e663633ea%2Fhypersim-welcome-interface.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

A new design can be created using the **Create a New Empty Design** or **Create a New Document from Template** options in the **File** menu, or by selecting **New** from **File > New**.

A new design initially consists of an empty circuit with a single page. This page appears in a circuit window and is assigned a default name. The **New** command does not automatically create a file on disk; the design exists only in memory until it is saved using **Save As** from the **File** menu or the **Home** ribbon.

To create a circuit schematic, begin by placing one or more devices in the circuit window, then connect the device pins using signal connections.

### Create the design from a template

HYPERSIM does not include a fixed set of templates; instead, it displays the templates available in the designated **Templates** folder. The default template file, **HYPERSIM.ecf**, is located in the program’s Templates directory.

A template may include various initial settings and elements—such as sheet borders, title blocks, and configuration options—to help you get started quickly. Once you are familiar with HYPERSIM’s basic functionality, you can create your own templates tailored to your needs. Templates are part of HYPERSIM’s open architecture and should be used carefully to avoid corrupting simulation data or modifying essential built-in attributes.

Keep in mind that software updates may modify the built-in template files. If you have created custom templates based on an existing template, you may need to update them to incorporate new attributes or settings. While some updates can be applied using patch scripts, more complex changes may require recreating your template by applying your customizations to the latest version of **HYPERSIM.ecf**.

For more information, refer to [**Design Templates**](https://github.com/Opal-RT-Technologies/product-docs-hypersim/tree/release-2026.4/model-and-simulation/edit-a-model-schematic/page-1.md) section.

## Save the design

An open design can be saved to disk using the standard **Save** and **Save As** commands in the **File** menu (or from the **Home > File** toolbar).

* The **Save** command writes the circuit to the file that was most recently opened or saved. This option is disabled if no file is currently associated with the design—for example, when a new design has not yet been saved.
* Selecting **Save As** opens a standard file dialog prompting you to enter a name for the new file. By default, the file name corresponds to the current title of the circuit window—that is, the name of the most recently opened or saved file.

{% hint style="danger" %}
**Avoid saving your project in directories managed by OneDrive or other cloud synchronization services**, as this may cause file integrity, versioning, or accessibility issues.

**Avoid using paths that contain spaces or special characters** when selecting a custom directory, as they may lead to compatibility issues with certain tools and workflows.
{% endhint %}

HYPERSIM manages several types of files, the most important of which is the **design file** containing all schematic data.

<table data-search="false"><thead><tr><th>Description</th><th>File Extension</th><th>More Information</th></tr></thead><tbody><tr><td><strong>Design files and sheet template files</strong></td><td>ecf</td><td>Design structure</td></tr><tr><td><strong>Symbol Library Files</strong></td><td>clf</td><td>About device symbols</td></tr><tr><td><strong>Report script files</strong></td><td>rfm</td><td>HYPERSIM export script language files.</td></tr><tr><td><strong>JavaScript files</strong></td><td>js</td><td>Scripting method in HYPERSIM based on JavaScript and HYPERSIM extensions to JavaScript.</td></tr><tr><td><strong>Initialization files</strong></td><td>ini</td><td></td></tr></tbody></table>

### **Backup procedures and timed Auto-Save** <a href="#backup-procedures" id="backup-procedures"></a>

HYPERSIM provides several backup features that allow you to tailor your backup strategy to meet your specific requirements.

In the **Options ribbon**, click on **Auto Backup Options..** command

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-06c9f215fdae794ec7602d2af53eabc2778b45ba%2Fauto-backup-options.png?alt=media" alt="" width="414"><figcaption></figcaption></figure>

When **auto-backup** is enabled, the following sequence occurs each time you use the **Save** command while a circuit file is open:

1. The existing design file is renamed by appending **\_Tag for backup file** and a timestamp in the format **\_year\_month\_day\_hour\_minute** between the file name and the extension to create a backup copy. The timestamp reflects the date and time the backup was created.
2. The current design is then saved as a new file using the original file name in the same directory.

The newly saved file retains the original file’s *creation date*, preserving its historical timestamp.

If a disk failure occurs (such as disk full) while the file is being saved, the existing file will already have been renamed to "design\_autobackup\_year\_month\_day\_hour\_minute" and will not be automatically switched back to its original name by the program.

**Save reminders** allows you to request a prompt to save the design every time a specified number of minutes have elapsed.

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

At the appointed time, a box will give you a choice of:

* Saving the file. This will also create an auto-backup file, as described above, if enabled.
* Postponing until another interval elapses.
* Disabling timed auto-save completely.
* Note that if you choose the last option, timed auto-save will be disabled until you quit and restart the program.

### **Revert to a saved file** <a href="#reverting-to-a-saved-file" id="reverting-to-a-saved-file"></a>

The **Revert** command in the File menu reloads the current design from the file on disk to which it was last saved or from which it was last opened. If changes have been made since the last save, you will be prompted to confirm before those changes are discarded.

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

The **Close** command in the **File** menu closes all circuit windows associated with the current design and removes the design from memory. If the design is hierarchical, all hierarchy levels are closed.

If changes have been made since the last **Open** or **Save**, you will be prompted to save them before closing.

The same result can be achieved by clicking the **“X”** button on the last circuit window tab.

## **Deleting a design** <a href="#deleting-a-design" id="deleting-a-design"></a>

HYPERSIM does not provide a built-in command to delete a design file. All design information is stored within a single file, which can be removed using Windows Explorer or a similar file management tool.

Deleting this file permanently removes all data associated with the design. In addition to the design file, HYPERSIM generates related files and directories for simulation purposes. These are stored in a folder located in the same directory as the design file and use the same name, with the suffix **\_hyp** appended.


---

# 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/create-and-manage-designs.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.
