> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/base64.md).

# Base64

## Description

The Base64 part is used to encode and decode binary data by treating it numerically and translating it into a Base64 representation so that it's more easily transmitted in things like e-mail and HTML form data.

## Use

Base64 encoding schemes are commonly used when there is a need to encode binary data that needs be stored and transferred over media that are designed to deal with textual data. This is to ensure that the data remains intact without modification during transport. Base64 is used commonly in for a number of operations, including sending email via MIME and storing complex data in XML.

The LogicNets Base64 part can be created by performing the following actions:

* Open the logicnet in the LogicNets Designer where you want to use the Base64 part.
* With your mouse in the logicnet Viewer screen (where you build your logicnets), right-click your mouse.
* Select "add node".
* Select "Process" (depending on the framework, you may also need to select "Base64" from the popup menu)
* Double-click on the newly added node to open the Editor pane. You may have to increase the size of the pane to see each of the tabs at the top. (Note: If the project is based on the framework, you may see the options of the Base64 part without needing to complete Step 6.)
* Click "text manipulation" and pull down to select "base64 encoder/decoder".
* Complete the parameters and click "save".

## Editor Fields

| Tab   | Field Name         | Description/Use                                                                                                             | Type/Options     | Optional/Mandatory |
| ----- | ------------------ | --------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------ |
| Basic | Operation Type     | This is the dropdown menu that tells the system to **Encode** or **Decode** the text.                                       | Text             | Mandatory          |
| Basic | Single Line Output | This is where you specify the type of output you want to have--either single-line text or not.                              | Text             | Optional           |
| Basic | Input Path         | This is where you define the text or provide a data object that will contain the text.                                      | Data Object/Text | Mandatory          |
| Basic | Output Path        | This is where you define the name of the place or variable name that will hold the converted text. This holds your results. | Data Object/Text | Mandatory          |

## Example

For an example of using the Base64 part, please download and import the following [sample project](/release-9/example-gallery/example-projects-for-parts/base64-example-project.md) in your workspace


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/base64.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.