> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/core-workflows/modules.md).

# Modules

The module browser is where most people start.

It is both the public catalogue and the front door to your own workspace.

Browsing is public. Adding modules to your collection or using collection-driven actions requires a signed-in account.

![Modules browser on iPad Pro](/files/naSCEMQEO6kXk4nxfG3k)

## What you can do here

* browse the public module database
* search for modules by name, manufacturer, description, and tags
* filter by module size, format, and other structured metadata
* inspect module details before adding anything to your workspace
* add owned modules to your collection
* open manuals quickly when they are available
* discover related public racks and patches
* contribute missing data when something is not in the catalogue yet

## What module detail pages include

Depending on the module, the detail page can include:

* manufacturer
* format and size
* panel images
* power information
* I/O information
* tags and descriptive metadata
* links to manuals
* public racks using the module
* public patches using the module

Manual links only appear when a module has complete enough data and a manual URL has actually been added.

The related racks and patches sections show public examples only.

## Add a module to your collection

1. Create an account or log in.
2. Open **Modules**.
3. Find a module you own.
4. Open the detail page.
5. Use the add action to save it to your collection.

Once a module is in your collection, it becomes available across the rest of the app.

## Why the collection matters

Your collection is not just a wishlist. It powers:

* rack planning
* patch capture
* manual shortcuts in your user area
* a more realistic picture of your real system

If you skip this step, your racks and patches will feel more like disconnected drafts than reflections of your real system.

## Missing module? Add it

If the database does not contain a module yet, use **Submit New Module**.

That helps both the public catalogue and your own workflow, because once the module exists in the library, it becomes usable everywhere else in Patcher.

Module data coverage is still improving. If a module exists but important details are missing, improving that module helps the rest of the workflow too.

## Panel images and manuals

Some modules include multiple panel images or variants. That matters when the physical look of the module affects your planning or rack screenshots.

Manual links become more useful as your collection grows, because Patcher also surfaces those manuals in User Area.

Not every module currently has a manual link or complete metadata, so treat missing data as a reason to improve the record, not as proof the feature is unavailable.

## Best way to use Modules

1. Search for hardware you already own.
2. Add that hardware to your collection.
3. Check manuals and metadata while you are there.
4. Use the collection as the source for racks and patches.

## Related pages

* [Collection](/core-workflows/collection.md)
* [User Area](/core-workflows/user-area.md)
* [Racks](/core-workflows/racks.md)
* [Patches](/core-workflows/patches.md)


---

# 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://docs.patcher.xyz/core-workflows/modules.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.