Documentation

​
​

Development

User Acquisition

Monetization

Industry

Asset Transformer Studio

2026.5.0

Supported
​

User Manual

Python API

Changelog

Asset Transformer Studio

2026.5.0

Supported
​
​
​
Get started
  • About Asset Transformer Studio
  • Getting started
  • Additional Resources
User Interface
  • Overview
  • Menu Bar
  • Toolbars
  • Window
  • Customizing the User Interface
Data Preparation Fundamentals
  • Overview
  • General Information
  • Typical Data Preparation Workflow
  • About 3D Models Types
  • About the Product Structure (Tree)
  • About Occurrences
  • About Instances & Prototypes
  • About Face and Vertex Normals
  • About UVs
  • About Tessellation
  • About Decimation
  • About Animation
  • Glossary
Working With Asset Transformer Studio
  • Overview
  • Videos and Tutorials
  • Supported File Formats
  • Importing Files
  • Exporting Files
  • Scripting With the Python API
  • Interrupting a Process
  • Plugins
    • Creating a Plugin
    • Running a Plugin
    • Managing Plugins
    • Publishing a Plugin
    • Plugins Shortcuts
  • Errors in Asset Transformer Studio
Python API Reference
  • Overview
Changelog
  • Changelog
  1. Asset Transformer Studio
  3. Working With Asset Transformer Studio

Plugins

Extend Asset Transformer Studio with custom plugins
Read time 2 minutes
Last updated 10 hours ago
Plugins menu example
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, which can be modified in the Scripting Editor or using your favorite IDE (see Creating a Plugin), with the help of the API Reference.
  • For you: Please contact Unity 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, 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) — 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 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
  • Scripting With the Python API
  • Running a Plugin
  • Plugins and Menu Customization
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Why plugins?

    • How are plugins developed?

    • Editable versus Published plugin

    • Plugins folder locations

    • Related topics