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)

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

Example Input (Decode)

{
    "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)

{
    "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)

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