# Base64 Encoder & Decoder (`rixin/base64-encoder-decoder`) Actor

From $0.1/1k requests. Encode text or files to Base64, decode Base64 back to text or binary files. Perfect for data transfer, API payloads, email attachments, and image embedding. Batch process multiple items in one run. Supports text and files. Fast, reliable encoding solution.

- **URL**: https://apify.com/rixin/base64-encoder-decoder.md
- **Developed by:** [Rixin Sc](https://apify.com/rixin) (community)
- **Categories:** Developer tools, Automation, Integrations
- **Features:** Limited permissions
- **Stats:** 136 total users, 7 monthly users, 96.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Base64 Encoder & Decoder

Encode text or files to Base64, or decode Base64 back to text or binary files. Fast, reliable, and easy to use for data transformation.

### What does Base64 Encoder & Decoder do?

Base64 Encoder & Decoder converts your data to and from Base64 encoding. You can encode plain text strings or files from any URL. The actor processes multiple items in a single run and outputs the result for each item.

- **Text Encoding**: Encode any plain text string to Base64
- **File Encoding**: Encode files from any URL (direct download links)
- **Text Decoding**: Decode Base64 strings back to plain text
- **File Decoding**: Decode Base64 to binary files saved in key-value store
- **Batch Processing**: Process multiple items in a single run

### Use Cases

- **Data Transfer**: Safely transfer binary data through text-only channels
- **API Payloads**: Encode binary data for JSON APIs
- **Email Attachments**: Prepare files for email embedding
- **Image Embedding**: Convert images to data URIs
- **Configuration Storage**: Store binary data in text-based config files

### Input

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `mode` | string | Yes | Operation mode: "encode" or "decode" |
| `textInputs` | array | No | List of text strings to encode/decode |
| `fileUrls` | array | No | List of file URLs to download and process (supports advanced HTTP options) |
| `outputAsFile` | boolean | No | When decoding, save output as file in KV store (default: false) |

#### Example Input (Encode)

```json
{
    "mode": "encode",
    "textInputs": ["Hello World", "Another string"],
    "fileUrls": [
        { "url": "https://example.com/image.png" }
    ]
}
```

#### Example Input (Decode)

```json
{
    "mode": "decode",
    "textInputs": ["SGVsbG8gV29ybGQ="],
    "outputAsFile": false
}
```

#### Advanced File URL Options

The `fileUrls` field supports full HTTP request configuration for each URL:

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `url` | string | Yes | The URL to fetch |
| `method` | string | No | HTTP method (GET, POST, PUT, etc.). Default: GET |
| `headers` | object | No | Custom HTTP headers to send with the request |
| `payload` | string | No | Request body for POST/PUT requests |
| `userData` | object | No | Custom data passed through for your reference |

#### Example Input (Advanced with Auth)

```json
{
    "mode": "encode",
    "fileUrls": [
        { "url": "https://example.com/public-image.png" },
        {
            "url": "https://api.example.com/protected-file",
            "method": "GET",
            "headers": {
                "Authorization": "Bearer your-token-here"
            }
        },
        {
            "url": "https://api.example.com/generate-pdf",
            "method": "POST",
            "payload": "{\"template\": \"invoice\"}",
            "headers": {
                "Content-Type": "application/json"
            }
        }
    ]
}
```

### Output

Each processed item produces a dataset record with:

| Field | Description |
|-------|-------------|
| `input` | The original input (text preview or file URL) |
| `inputType` | Type of input: "text" or "file" |
| `mode` | Operation mode: "encode" or "decode" |
| `output` | Base64 string (encode) or decoded text (decode) |
| `outputFileKey` | Key in KV store when outputAsFile is true |
| `inputSizeBytes` | Size of input data in bytes |
| `outputSizeBytes` | Size of output data in bytes |
| `processedAt` | ISO timestamp of when processing completed |
| `error` | Error message if processing failed, null otherwise |

#### Example Output (Encode)

```json
{
    "input": "Hello World",
    "inputType": "text",
    "mode": "encode",
    "output": "SGVsbG8gV29ybGQ=",
    "outputFileKey": null,
    "inputSizeBytes": 11,
    "outputSizeBytes": 16,
    "processedAt": "2024-01-15T10:30:00.000Z",
    "error": null
}
```

### Pricing

This actor uses pay-per-event pricing:

| Event | Price | Description |
|-------|-------|-------------|
| Text Processed | $0.0001 | Charged for each text string encoded/decoded |
| File Processed | $0.0002 | Charged for each file fetched and processed |
| File Generated | $0.0002 | Charged when decoded output is saved as file |

**Example costs:**

- 1,000 text encodes: $0.10
- 1,000 file encodes: $0.20
- 1,000 decodes to file: $0.30 (file-processed + file-generated)

### Integrations

Works with all Apify integrations:

- **Apify API**: Trigger runs programmatically
- **Webhooks**: Get notified when runs complete
- **Zapier/Make**: Connect with automation workflows

### FAQ

**Q: What's the difference between encode and decode?**
A: Encode converts binary/text to Base64 string. Decode converts Base64 string back to original data.

**Q: When should I use outputAsFile?**
A: Use it when decoding binary data (images, PDFs, etc.) that can't be represented as text.

**Q: What's the maximum file size?**
A: Files are limited by available memory. The actor uses 256-1024 MB, supporting larger files.

**Q: Can I process files from any URL?**
A: Yes! Any publicly accessible URL is supported. The file will be downloaded and processed.

**Q: What encoding standard is used?**
A: Standard Base64 encoding (RFC 4648) with A-Z, a-z, 0-9, +, / characters and = padding.

# Actor input Schema

## `mode` (type: `string`):

Choose whether to encode data to Base64 or decode Base64 back to original data.

## `textInputs` (type: `array`):

Enter text strings to process. For encoding: enter plain text. For decoding: enter Base64 strings.

## `fileUrls` (type: `array`):

URLs to files to process. Supports GET (default) and other HTTP methods with custom headers and payload.

## `outputAsFile` (type: `boolean`):

When decoding, save the output as a file in the key-value store instead of returning as text. Useful for binary data like images.

## Actor input object example

```json
{
  "mode": "encode",
  "textInputs": [
    "Hello World",
    "Apify is awesome!"
  ],
  "fileUrls": [],
  "outputAsFile": false
}
```

# Actor output Schema

## `results` (type: `string`):

URL to the dataset containing all processed items

## `decodedFiles` (type: `string`):

URL to the key-value store containing decoded files (when outputAsFile is true)

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "textInputs": [
        "Hello World",
        "Apify is awesome!"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("rixin/base64-encoder-decoder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "textInputs": [
        "Hello World",
        "Apify is awesome!",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("rixin/base64-encoder-decoder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "textInputs": [
    "Hello World",
    "Apify is awesome!"
  ]
}' |
apify call rixin/base64-encoder-decoder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rixin/base64-encoder-decoder"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/WrWIyybUXHy43Oygq/builds/mqk91J3g0stVDx9hc/openapi.json