Electric current converter
One kiloampere is 1000 amperes, and one microampere is a millionth of an ampere. Convert current between amperes, milliamperes, microamperes, kiloamperes and abamperes for component datasheets, circuit-board notes, breaker ratings and homework. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- Source unit
- A
- Target unit
- mA
- Result
- 1,000
- From label
- ampere
- To label
- milliampere
- Amperes
- 1
An electric current converter turns a quantity written in one current unit into another without hunting conversion tables or rewriting spreadsheet formulas.
Supported units and how the conversion is computed
The converter accepts five electric current families under stable canonical codes: A for the SI ampere, mA for the milliampere, uA for the microampere (ASCII form; Greek mu micro symbols are also accepted), kA for the kiloampere, and abA for the abampere of the CGS electromagnetic system, historically also called the biot. Factors follow SI and conventional engineering standards: one milliampere is exactly one thousandth of an ampere, one microampere is exactly one millionth of an ampere, one kiloampere is one thousand amperes, and one abampere is exactly ten amperes.
Because the intermediate is always amperes, converting A to B and B to A is consistent up to the published rounding of twelve decimal places, and there is no pairwise matrix that can drift out of sync. Voltage, charge, power, and resistance units are intentionally out of scope so electronics, lab, and power-engineering users get predictable current-only results under one clear convention.
Everyday uses in electronics and power work
Use the free in-browser electric current converter when you need a quick amperes-to-milliamperes, microamperes-to-amperes, or kiloamperes-to-abamperes check while reading a datasheet, PCB design note, lab procedure, power-system drawing, or homework problem. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a unit library, or a desktop calculator pack. Source inputs follow the same retention rules as other KIT parse items, and results are safe to cache because the algorithm is fully deterministic.
Authors shipping mobile apps or chatbots can map the result and formula fields directly into cards that show both the number and the conversion path students, technicians, and engineers expect on paper.
What you can do with it
Electronics design and PCB work
Convert milliamperes and microamperes to amperes so LED, sensor, and regulator datasheets share one SI view without hand-written factors in design notes.
Power systems and industrial equipment
Normalize kiloamperes and amperes in bus-bar ratings, breaker specs, and plant logs when drawings mix SI multiples and legacy labels.
FAQ
Which electric current units does this converter support?
Amperes (A), milliamperes (mA), microamperes (uA or µA), kiloamperes (kA), and abamperes (abA, also biot).
How do I convert 1 abampere to amperes?
The response result field is 10, plus an amperes intermediate and a readable formula.
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the electric current converter free?
The browser tool runs free on your device.
Can I enter a negative current?
Yes. A negative value keeps its sign, which is useful for current direction in circuit analysis or sensor logs, and zero converts to zero in every unit.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/electric-current \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"A","to":"mA"}'const res = await fetch("https://api.kit.forhosting.com/conv/electric-current", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "A",
"to": "mA"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/electric-current",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "A",
"to": "mA"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/electric-current", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"A","to":"mA"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"A","to":"mA"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/electric-current", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 1,
"from": "A",
"to": "mA"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.electric_current",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when pipelines need the same contract from servers and automation.
Supported units and how the conversion is computed
Friendly aliases such as amp, amps, ampere, amperes, milliamp, milliamps, milliampere, milliamperes, microamp, microamps, microampere, microamperes, kiloamp, kiloamps, kiloampere, kiloamperes, abamp, abampere, abamperes, biot, and biots are normalized case-insensitively so forms and APIs can pass either short codes or full names. Every request multiplies the input value by the exact amperes-per-unit factor for the source, then divides by the amperes-per-unit factor for the target.
Request shape, response fields, and unknown-unit errors
The error message names the bad field and lists the supported set so clients can correct forms without guessing. Negative values are allowed when you need signed current direction in circuit analysis or sensor pipelines; zero converts cleanly to zero in every target unit. Send a JSON body with three required fields: value as a finite number, from as the source unit string, and to as the target unit string. Aliases amount and quantity are accepted for value; unit_from and source for from; unit_to and target for to. On success the response echoes the canonical from and to codes, human-readable from_label and to_label strings, the converted result, the intermediate amperes quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag electric_current_si, and the fixed list of units_supported. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, and any token that does not map to a supported unit fail with invalid_input and are not charged after the engine rejects the request. Identical inputs always yield identical JSON because the path is pure arithmetic with no randomness, no remote lookup, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests. Microampere-scale results and kiloampere-scale results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate amperes product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when an electronics CAD plugin, test-bench LIMS, battery management tool, motor controller, physics homework checker, or instrumentation pipeline must convert current at scale under a stable KIT contract at $0.002 per successful item; validation failures that raise invalid_input do not consume balance after rejection. Pair this endpoint with voltage or power converters when a product pipeline needs several electrical measure families, or call it alone when search traffic is specifically for electric current conversion—amperes, milliamperes, microamperes, kiloamperes, and abamperes—rather than a general unit switchboard.
Integration use cases
Lab metrology and CGS archives
Convert abamperes and biots to amperes for historical instrument records and class problems with a prepaid, deterministic API and clear invalid_input on unknown units.
Technical questions
How many milliamperes is one ampere?
Exactly 1000 mA. Send value: 1, from: "A", to: "mA" to see it in the result field.