---
schema_version: "1"
id: 1635387a2b55d17f1ae11040f5ab70ff25a1b908678d359fde651a0ae209ce9f
title: Move Transformations to Separate Files
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/move-transformations-separate-file-studio-task.md
canonical_url: https://docs.mulesoft.com/studio/move-transformations-separate-file-studio-task
source_site: docs.mulesoft.com
content_type: documentation
content_hash: e12b67a890ed7a1f718b7d93347bce6bdab4c3d6f89a76401aab4ad07bed29e9
description: MuleSoft Documentation Site
latest: true
---
---
product: Studio
---

# Move Transformations to Separate Files

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

By default, the DataWeave code from a Transform Message component is expressed inline within your
Mule XML file. You can instead keep each in a separate file ( `.dwl` ) and have your XML reference
them. These files are packaged with your Mule application when built.

To export the DataWeave code to a `.dwl` file:

1.  Click the **Edit Current Target** button.

    ![Code showing a list of payment data fields, including coin, payments, and type](/mulesoft/current/en-us/studio/_images/dw-multiple-outputs-edit.png)

2.  Select the 'File' radio button.

    ![A dialog box with options for selecting a target file](/mulesoft/current/en-us/studio/_images/dataweave-externalfile2.png)

3.  Type a name for your `.dwl` file.

4.  Click OK.

A file is created under the `src/main/resources` folder in your project containing your DataWeave
code.

## See Also

- [DataWeave language](https://docs.mulesoft.com/mule-runtime/latest/dataweave)

- [Transform Message Component](https://docs.mulesoft.com/studio/transform-message-component-concept-studio)