# Plugins

> Extend Asset Transformer Studio with custom plugins

![Plugins menu example](/api/media?file=/asset-transformer-studio/2026.5.0/media/STUDIO_Menu_Plugin-Example.jpg)

Extend Asset Transformer Studio's core features by encapsulating your data preparation process using **plugins**.

A plugin is composed of:

* One or several **Python script files** (.py): they embed the data preparation code to execute
* An **XML file** (.xml), used to provide an interface, which exposes the arguments to feed as input/output to the scripts
* Python modules dependencies

## Why plugins?

Plugins can be created to add custom functionalities and behavior to Asset Transformer Studio, by creating dedicated data preparation tools with their own interface, menu, or button, for example to automate repetitive tasks.

## How are plugins developed?

Plugins can be developed:

* **By you**: Plugins can be easily created from a Template accessible in the [Plugins menu](/asset-transformer-studio/2026.5.0/manual/user-interface/menu-bar/plugins-menu.md), which can be modified in the Scripting Editor or using your favorite IDE (see [Creating a Plugin](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/creating-a-plugin.md)), with the help of the [API Reference](/asset-transformer-studio/2026.5.0/api/python/studio_functions.md).
* **For you**: Please [contact Unity](https://create.unity.com/unity-for-industries?sfcid=7015G000000KFkqQAG\&sflsa=2023-03-Pixyz-Studio-trial-contact-us) if you are interested in the creation of a bespoke scenario, based on your specific data preparation process.

## Editable versus Published plugin

By default, a plugin is editable: all its files are accessible and can be modified, within Asset Transformer Studio using the [Scripting Editor](/asset-transformer-studio/2026.5.0/manual/user-interface/window/scripting.md), or outside using an IDE. A plugin that can be edited is an `Editable plugin`.

A plugin can be published in the form of a binarized archive file, with a .pxzext extension. It is then called a `Published plugin`, easier to store and exchange with other Asset Transformer Studio users.

## Plugins folder locations

In order to be loaded and executed in Asset Transformer Studio, plugins *must* be placed in one of the following predefined locations on a computer:

* `ProgramData` folder (`%programdata%/PixyzStudio/plugins`): place a plugin folder here to make it available for all computer users (see [Creating a Plugin](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/creating-a-plugin.md)) — **recommended location**
* `AppData` folder (`%appdata%/PixyzStudio/plugins`): place a plugin folder here to restrain plugin access to the concerned user (see [Creating a Plugin](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/creating-a-plugin.md))
* Asset Transformer Studio installation directory (`PixyzStudioInstallationDirectory/bin/plugins`): folder where default plugins are located, when existing — **do not modify**

At startup, Asset Transformer Studio loads all the plugins located in these 3 folders.

> **Important:**
>
> Plugins cannot be loaded from a different location than these 3 locations!

## Related topics

* [Creating a Plugin](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/creating-a-plugin.md)
* [Scripting With the Python API](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/scripting-with-the-python-api.md)
* [Running a Plugin](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/running-a-plugin.md)
* [Plugins and Menu Customization](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/plugins/plugins-shortcuts.md)