# Byte to human readable

## Description

This operation converts a size in bytes into a more human-friendly format, such as kilobytes (KB), megabytes (MB), gigabytes (GB), and so on. This operation is especially useful for interpreting file sizes or data storage values.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](/files/lPHCVhp93aYrWgLIlhNp) - Sizes in bytes to be transformed. They must be strings that represent integer numbers.

### Output data

![](/files/3itBmKrRqasWlG3dGBlS) - Resulting human-readable strings.

***

## Example

Suppose you want to convert a series of events that represent **sizes in bytes** into **human-readable strings**:

1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **Byte to Human Readable**.
3. Give your **Output field** a name and click **Save**. The byte sizes in your input field will be transformed into human-readable strings. For example:

```
Input data - "134367"

Output data - "131.22 KiB"
```

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/utils/byte-to-human-readable.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.