Skip to main content

Alteryx File Types

Here is a list of file extensions native to Alteryx:

Alteryx Workflows

Alteryx Data Files

Special Files

License Files

.yxmd (Workflow)

.yxdb (Alteryx Database)

.yxwv (App Values)


.yxwg (Workflow group)

.cydb (Calgary Database)

.yxft (Field Types)


.yxmc (Macro)

.cyidx (Calgary Index)

.yxbe (Browse Everywhere data)


.yxwz (Analytic App)

.rptx (Allocate reports)

.bak (Backup copy of a workflow)


.yxzp (Packaged Workflow)

.vvf (Allocate virtual variables)

.pcxml (Composer file)


.yxi (Packaged Tool)

.aws (Allocate workspace file)

.log (Error log files)

.indbc (Packaged In-DB connections)

.bin (Manual Flexera authentication)

.yxtd (Workflow Template)

.yxlang (Localization files)

.yxtc (Macro Template)

CASS.ini (CASS directory information)

.yxtz (App Template)

Alteryx Workflow Files

.yxmd (Workflow)

An Alteryx workflow represents a repeatable workflow process and has a file extension of .yxmd. All of the inputs, outputs, and tool configurations are saved within a single Alteryx workflow so you can open and run the workflow multiple times.

For more information, go to Workflow Configuration and Build Workflows.

Workflow Template

If you save a workflow as a template, the template uses the .yxtd file extension. Go to Templates to learn more.

.yxwg (Workflow Group)

A workflow group represents multiple workflows that you can save and open as one file. You can only create a workflow group of existing, locally-saved workflows.

For more information, go to Workflow Management.

.yxmc (Macro)

A macro is a workflow that you can run as a single tool within another workflow. With the macro-design settings, a developer can specify parameters so a user has options to configure the workflow from a single tool. Once you set the workflow type as a macro, the options available in the Workflow Properties window change.

Go to Macros for more information about the different types of macros.

Macro Template

If you save a macro as a template, the template uses the .yxtc file extension. Go to Templates to learn more.

.yxwz (Analytic App)

Developers can create an Analytic App in Designer for users to run in the Alteryx Analytic App environment. The developer creates a workflow in Alteryx, specifies a series of parameters that define the user environment, and the original design workflow is updated with the user's specifications. Access Analytic Apps from a web browser if saved to the Gallery—or via a server or desktop installation. Use the Analytic App design settings to specify parameters so a user has options to configure the workflow from a custom user interface.

Go to Analytic Apps for more information.

App Template

If you save an analytic app as a template, the template uses the .yxtz file extension. Go to Templates to learn more.

.yxzp (Packaged Workflow)

A .yxzp file is a workflow package that includes an Alteryx workflow (in other words, .yxmd, .yxmc, or .yxwz) and all its dependencies zipped into a single file. You can import this file into Alteryx, which ensures that you can easily distribute and share workflows with users.

Go to Workflow Management for more information.

.yxi (Packaged Tool)

A .yxi file is a package that includes an Alteryx tool and all of its dependencies zipped into a single file. When this file is installed in Alteryx Designer, from an external source such as the Alteryx Public Gallery (, the tool is added to the tool palette in the category specified.

The .yxi file, and any supporting macros required for the tool to work, are installed in:


Administrators can optionally choose to install a .yxi tool for all users, in which case the tool is installed in:


A .yxi file must be installed before a workflow containing that tool can be run.

Alteryx Data Files

.yxdb (Alteryx Database)

The Alteryx database format (.yxdb) is a file type that can hold data fields, values, and spatial objects. The .yxdb format is the most efficient file type for reading and writing in Alteryx because it has no size limit, is compressed for maximum speed, and includes additional metadata that references the source of the data and how the data was created. While there is no limit to the number of records or file size, there is a record size limit of 2 GB in a 64-bit environment.

Go to Alteryx Database File Format for more information.

.cydb (Calgary Database)

The Calgary database (.cydb) is a data file that uses indexing methodology to quickly retrieve records. A database index is a data structure that improves the speed of data retrieval operations on a database table. Indexes can be created using one or more columns of a database table, providing the basis for both rapid random lookups and efficient access of ordered records. There is a 2^31 limit on the number of records in a Calgary database (approximately 2 Billion). It is designed for around 100-300 million records.

Go to Calgary for more information.

.cyidx (Calgary Index)

The Calgary index (.cyidx) is a dependency file for a Calgary database (.cydb). When a .cydb is written, an index file is created for each field of the Calgary database. The index makes it possible to quickly retrieve records based on specific queries configured by the user.

Go to Calgary Indexes for more information on how Alteryx creates indexes specific to different data types.

Special Files

.yxwv (App Values)

The Alteryx App Values file is a .xml file that contains values and syntax that update an Analytic App. Some Analytic Apps can have a lot of configuration options and users might want to save their specifications to use over and over again. They can save those selections to a .yxwv file so they do not need to populate the Analytic App interface each time they run the Analytic App. You can save and open a .yxwv file from the Analytic App interface.

.yxwv files are not encrypted. Any passwords included in them will be stored as clear text.

Go to Analytic Apps for more information.

.yxft (Field Type)

The Alteryx Field Type file is a text file that describes the file configuration of field names and field types. Once saved, the .yxft can be loaded via the Select tool or any tool with an embedded select.

From the Options menu of any Select tool, the Save/Load options create or access a .yxft file you've created.

.bak (Backup Copy of a Workflow)

A backup file is created as soon as a workflow is edited and saved. The .bak file is the workflow in its state prior to the most recent save. The .bak file is created in the same directory as the edited workflow and carries the same name.

.pcxml (Composer File)

A .pcxml file contains a proprietary language used by Alteryx for reporting purposes. Alteryx can read and render a .pcxml file for reporting output, but users are not encouraged to use this file type. Instead, create report snippets using the Reporting tools and save them to a .yxdb file or a final presentation output format.

.log (Log Files)

Log files are created when the Alteryx engine, or a core component of the Alteryx engine, throws a fatal error. The log file contains information about where or how the failure occurred. If you report a fatal error to technical support, you may be asked to retrieve the log file. Log files are written to the following directory:


Application name refers to the area of Alteryx that is throwing the error. For example AlteryxEngine, AlteryxCass, SrcLib_Dllx64, etc.

These error messages produce log files:

  • An Unhandled Exception Error occurred.

  • You have found a bug. Replicate, then let us know. We shall fix it soon.