---
schema_version: "1"
id: cc89f5d60210fd12dff4dc505ad1f7e12a2c1ca2fcec8acc914877c0ba272c38
title: Move Transformation to Separate Files (Anypoint Studio)
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/latest/transform-move-transformations-separate-file-studio-task.md
canonical_url: https://docs.mulesoft.com/mule-runtime/latest/transform-move-transformations-separate-file-studio-task
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8dbc385e1a7967826062d6124c2a19e37d435bb99fa4cf9657577aa7996d77c4
description: MuleSoft Documentation Site
release: "4.13"
latest: true
---
---
product: Mule Runtime
version: 4.13
is-latest-version: true
---

# Move Transformation to Separate Files (Anypoint Studio)

> 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.

    ![An edit icon in the Transform Message component](/mulesoft/current/en-us/mule-runtime/latest/_images/dw-multiple-outputs-edit.png)

2.  Select the **File** radio button.

    ![A target output payload with an option to choose a source code](/mulesoft/current/en-us/mule-runtime/latest/_images/dataweave-externalfile2.png)

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

    - 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/mule-runtime/latest/transform-component-about)