Number Base Converter

Convert numbers between any numeral base — binary, octal, decimal, hex, base32, base36, or any custom base from 2 to 62. Batch convert hundreds of numbers instantly with no proxy, no scraping, pure computation.

---

What does it do?

The Number Base Converter takes a list of numbers and converts each one to every target base you specify. It supports bases from 2 (binary) all the way to 62, handles arbitrarily large integers via BigInt, and produces a clean dataset of results you can download as JSON, CSV, or XLSX.

Whether you need to convert a hex color to decimal, translate binary machine codes to readable integers, or bulk-process IP addresses and memory addresses across numeral systems — this actor handles it instantly without spinning up a browser or making any network requests.

---

Who is it for?

🧑‍💻 Software developers — convert register values, memory addresses, bitmasks, and protocol constants between binary, hex, and decimal during debugging or reverse engineering.

🔬 Computer science students — practice and verify number-system conversions for coursework, homework, and exam prep.

🔐 Security researchers and CTF players — decode obfuscated values, shellcode bytes, or encoded flags from challenge data.

📊 Data engineers — normalize numeric identifiers across systems where some store in hex and others in decimal (database IDs, color codes, IP addresses).

🤖 Automation builders — integrate base conversion as a data-transformation step inside larger Apify workflows or Zapier/Make pipelines.

---

Why use it?

• ⚡ Instant results — pure in-process computation, no HTTP requests, no proxy costs
• 🔢 Any base 2–62 — not just the standard four; use base36 for compact IDs, base62 for URL-safe tokens
• 📦 Batch processing — convert thousands of numbers in a single run
• 🔗 Structured dataset output — download as JSON, CSV, or XLSX; integrate via API
• 💰 Near-zero cost — compute only, no proxy bandwidth; typical run costs $0.005–0.01
• 🛡️ Graceful error handling — invalid inputs are flagged in the error field rather than crashing the run

---

What data does it extract?

Each number you provide produces one dataset row with all requested base representations:

Field	Type	Description
input	string	The original input value as provided
fromBase	number	The source base used for parsing
binary	string	Base-2 (binary) representation
octal	string	Base-8 (octal) representation
decimal	string	Base-10 (decimal) representation
hex	string	Base-16 (hexadecimal) representation
base36	string	Base-36 (compact alphanumeric) representation
conversions	object	Map of all requested base conversions (e.g. {"base2": "…", "base16": "…"})
error	string|null	Error message if parsing failed; null on success

---

How much does it cost to convert numbers between bases?

The Number Base Converter uses pay-per-event (PPE) pricing — you only pay for what you use:

Event	FREE tier price	DIAMOND tier price
Run start (one-time)	$0.005	$0.0025
Per number converted	$0.00115	$0.00028

Example costs:

• Convert 100 numbers → $0.005 start + 100 × $0.00115 = $0.120
• Convert 1,000 numbers → $0.005 + 1,000 × $0.00115 = $1.155
• Convert 10 numbers (small batch) → approximately $0.017

Higher subscription tiers (Bronze through Diamond) receive up to 60% off per-conversion pricing. There is no monthly fee — you only pay when you run the actor.

Free plan estimate: Apify's free plan includes $5 of compute credits, which covers approximately 4,300 conversions.

---

How to convert numbers — step by step

1. Open the actor on Apify Store and click Try for free
2. In the Numbers field, enter the numbers you want to convert — one per line
3. Set Source base to the numeral system your input numbers are in (10 = decimal, 16 = hex, 2 = binary, etc.)
4. Set Target bases to the JSON array of bases you want output for, e.g. [2, 8, 10, 16, 36]
5. Toggle Uppercase output if you want hex digits as FF instead of ff
6. Toggle Include standard prefixes to prepend 0b / 0o / 0x to the relevant outputs
7. Click Start — the run typically completes in under 5 seconds
8. Download results from the Dataset tab as JSON, CSV, or XLSX

---

Input parameters

Parameter	Type	Default	Description
numbers	string[]	—	Required. List of number strings to convert
fromBase	integer	10	Source base (2–62). Use 10 for decimal, 16 for hex, 2 for binary
toBases	integer[]	[2,8,10,16,36]	Target bases for output. Each must be 2–62
upperCase	boolean	true	Output alphabetic digits in uppercase
includePrefix	boolean	false	Prepend 0b, 0o, 0x for bases 2, 8, 16

Supported prefix auto-stripping

When the fromBase matches the prefix convention, the prefix is automatically stripped from input values before parsing:

Prefix	Auto-stripped when fromBase
0x or 0X	16
0b or 0B	2
0o or 0O	8

---

Output example

Input: ["255", "1023", "DEADBEEF"] with fromBase: 10 / fromBase: 10 / fromBase: 16

[
  {
    "input": "255",
    "fromBase": 10,
    "decimal": "255",
    "binary": "11111111",
    "octal": "377",
    "hex": "FF",
    "base36": "73",
    "conversions": {
      "base2": "11111111",
      "base8": "377",
      "base10": "255",
      "base16": "FF",
      "base36": "73"
    },
    "error": null
  },
  {
    "input": "DEADBEEF",
    "fromBase": 16,
    "decimal": "3735928559",
    "binary": "11011110101011011011111011101111",
    "octal": "33653337357",
    "hex": "DEADBEEF",
    "base36": "X53YSN",
    "conversions": {
      "base2": "11011110101011011011111011101111",
      "base8": "33653337357",
      "base10": "3735928559",
      "base16": "DEADBEEF",
      "base36": "X53YSN"
    },
    "error": null
  }
]

---

Tips and best practices

💡 Use auto-prefix stripping — if your data already uses 0x or 0b prefixes, the actor will handle them correctly as long as fromBase matches.

💡 Large integers are supported — the actor uses JavaScript BigInt internally, so there is no precision loss for numbers larger than Number.MAX_SAFE_INTEGER (2^53).

💡 Batch similar inputs — group numbers by their source base and run one actor invocation per source base for cleanest results.

💡 Invalid inputs don't stop the run — each number is processed independently. If one is unparseable, its row will have error set and the rest continue normally.

💡 Use the conversions field for custom bases — if you need base 5 or base 13, it won't appear in the named convenience fields, but it will be in conversions["base5"].

---

Integrations

🔗 Zapier / Make automation

Connect the Number Base Converter to Zapier or Make to add base conversion as a step in larger workflows:

• Color pipeline: Receive hex color codes from a design system → convert to decimal RGB components → push to your database
• CTF/security workflow: Receive Base64-decoded bytes → convert each byte value from decimal to hex for shellcode analysis
• ID normalization: Pull IDs from a legacy system in hex → convert to decimal → write to a new database

🔗 Apify platform integration

Chain with other Apify actors using datasets:

1. Run a scraper that outputs hex-encoded values
2. Feed those values into Number Base Converter
3. Download the converted dataset as CSV

🔗 API integration

Use the Apify API to run the actor programmatically as a microservice for base conversion in your application's data pipeline.

---

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });

const run = await client.actor('automation-lab/number-base-converter').call({
    numbers: ['255', 'FF', '11111111'],
    fromBase: 10,
    toBases: [2, 8, 16],
    upperCase: true,
    includePrefix: false,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient(token="YOUR_APIFY_TOKEN")

run = client.actor("automation-lab/number-base-converter").call(run_input={
    "numbers": ["255", "FF", "11111111"],
    "fromBase": 10,
    "toBases": [2, 8, 16],
    "upperCase": True,
    "includePrefix": False,
})

items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL

# Start a run
curl -X POST "https://api.apify.com/v2/acts/automation-lab~number-base-converter/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "numbers": ["255", "1023", "65535"],
    "fromBase": 10,
    "toBases": [2, 8, 16],
    "upperCase": true
  }'

# Fetch results (replace RUN_ID and DATASET_ID from the response above)
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?token=YOUR_APIFY_TOKEN"

---

Use with AI assistants (MCP)

The Number Base Converter is available as an MCP (Model Context Protocol) tool, letting Claude and other AI assistants call it directly during conversations.

Claude Code (terminal)

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/number-base-converter"

Claude Desktop / Cursor / VS Code

Add to your MCP configuration JSON:

{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=automation-lab/number-base-converter",
      "headers": {
        "Authorization": "Bearer YOUR_APIFY_TOKEN"
      }
    }
  }
}

Example prompts

• "Convert these hex values to decimal and binary: FF, 1A2B, DEADBEEF"
• "I have a list of 32-bit binary strings from a log file — convert them all to hex for me"
• "Take this base36 compact ID and show me its decimal and hex equivalents"
• "Convert IP address components 192.168.1.1 to binary and hex"

---

Legality and terms of service

The Number Base Converter performs pure mathematical computation only. It makes no network requests, accesses no external websites, and does not scrape any data. There are no terms-of-service concerns — it is equivalent to running a calculator.

All input data you provide stays within the Apify platform's standard data handling policies.

---

FAQ

Q: What's the largest number I can convert? A: The actor uses JavaScript BigInt internally, which supports arbitrarily large integers with no precision loss. Numbers with thousands of digits are handled correctly.

Q: What happens if I enter an invalid number for the chosen source base? A: The invalid entry is skipped gracefully. Its dataset row will have all base fields set to null and an error field with a description of the problem. The rest of the numbers in the batch continue normally.

Q: Can I use it for floating-point numbers? A: No — the actor supports integers only. Decimal fractions (e.g., 3.14) are not supported. For floating-point base conversion you would need a specialized tool.

Q: Why does 0xFF work but FF gives an error with fromBase 10? A: FF contains alphabetic characters that are not valid in base 10. If your inputs are hex strings, set fromBase to 16. The 0x prefix is only auto-stripped when fromBase is set to 16.

Q: Can I convert to multiple bases at once? A: Yes — set toBases to an array like [2, 8, 10, 16, 36] and every number will be converted to all of those bases in a single run.

Q: The actor ran but produced fewer results than I expected. What happened? A: Check the error field in dataset rows — invalid inputs are written to the dataset with an error message rather than being silently dropped. Review your fromBase setting and ensure your input numbers only contain valid digits for that base.

---

Related scrapers

• Base64 Converter — Encode and decode Base64 strings in bulk
• Color Format Converter — Convert colors between HEX, RGB, HSL, HSB, and CMYK
• CSS Unit Converter — Convert px, em, rem, pt, vh, vw, cm, mm, in, pc units
• JSON Validator — Validate JSON strings and files for syntax errors
• URL Parser — Parse URLs into protocol, host, path, query, and fragment components