Volume charge density converter
Translate charge spread through a volume between ten units: 1 C/m³ is 0.000001 C/cm³, and every value passes through coulombs per cubic metre so the result matches both ways. Handy for plasma papers, electrostatics homework and beam lab notes. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- From
- C/m3
- To
- C/cm3
- Result
- 0.000001
- From label
- coulomb per cubic metre
- To label
- coulomb per cubic centimetre
- C per m3
- 1
Volume charge density measures how much electric charge is distributed through a given volume of space, plasma, dielectric, or charged fluid. Engineers, physicists, and students often receive values in coulombs per cubic metre from SI textbooks, coulombs per litre from process and chemistry notes, coulombs per cubic centimetre from older lab reports, or microcoulombs per cubic centimetre from plasma and beam literature—and need a trustworthy conversion without rebuilding factors by hand.
Supported units and exact conversion factors
The converter accepts ten volume charge density families under stable canonical codes: C/m3 for coulombs per cubic metre (SI), C/cm3 and C/mm3 for coulomb per cubic centimetre and millimetre, C/L for coulomb per litre, C/in3 and C/ft3 for coulomb per cubic inch and foot, plus mC/m3, uC/m3, nC/m3, and uC/cm3 for milli-, micro-, and nanocoulomb prefixes common in electrostatics and plasma work.
Volume factors follow SI definitions: one cubic centimetre is exactly ten to the minus six cubic metres, one cubic millimetre is ten to the minus nine, one litre is exactly one thousandth of a cubic metre, one cubic inch is exactly zero point zero two five four metres cubed, and one cubic foot is zero point three zero four eight metres cubed.
Prefix units scale charge only: one millicoulomb per cubic metre is one thousandth of a coulomb per cubic metre, one microcoulomb per cubic metre is one millionth, one nanocoulomb per cubic metre is one billionth, and one microcoulomb per cubic centimetre equals one coulomb per cubic metre. Because the intermediate is always C/m³, converting A to B and B to A is consistent up to the published twelve-decimal rounding, and there is no pairwise matrix that can drift out of sync.
Surface charge density, linear charge density, and raw electric charge are intentionally out of scope so volume-charge users get predictable ρ-only results under one clear convention.
Where this conversion saves you time
Use the free in-browser volume charge density converter when you need a quick C/m³ to C/cm³, C/L to C/m³, or µC/cm³ to C/m³ check while reading a plasma physics paper, electrostatics homework problem, charged-fluid process specification, or ion-beam laboratory procedure. 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, process engineers, and lab technicians expect on paper.
What you can do with it
Plasma and beam physics labs
Convert C/m³ and µC/cm³ readings between diagnostics, simulation codes, and SI reports so charge-cloud densities stay comparable across instruments.
Textbook and homework electrostatics
Students convert C/m³ problem statements into C/L or C/cm³ answers with exact SI litre and centimetre volume factors and clear errors on typos.
FAQ
How is C/L related to C/m³?
One litre is exactly 0.001 m³. The converter multiplies by 1000 so 1 C/L equals exactly 1000 C/m3 with stable twelve-decimal rounding.
What if I send an unknown unit?
The message names the bad field and lists supported units; validation failures are not charged.
Is the volume charge density converter free?
The browser tool runs free on your device.
Does it convert surface or linear charge density?
No. This capability only converts volume charge density ρ (charge per volume). Surface σ and linear λ charge densities are out of scope.
Why is one µC/cm³ the same as one C/m³?
The micro prefix divides the charge by a million, and a cubic centimetre is a millionth of a cubic metre. Both factors cancel, so the two units describe exactly the same density.
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/volume-charge-density \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"C/m3","to":"C/cm3"}'const res = await fetch("https://api.kit.forhosting.com/conv/volume-charge-density", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "C/m3",
"to": "C/cm3"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/volume-charge-density",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "C/m3",
"to": "C/cm3"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/volume-charge-density", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"C/m3","to":"C/cm3"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"C/m3","to":"C/cm3"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/volume-charge-density", 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": "C/m3",
"to": "C/cm3"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.volume_charge_density",
"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
This capability converts a numeric volume charge density from one supported unit to another with fixed SI volume definitions (inch exactly 0.0254 m, litre exactly 0.001 m³), routes every pair through C/m³ as the intermediate base, and returns deterministic JSON for APIs, SDKs, and free browser use. Unknown unit names fail with a clear invalid_input error so forms and pipelines never silently invent a factor.
Supported units and exact conversion factors
Friendly aliases such as C/m³, C/m^3, coulomb per cubic meter, microcoulomb/cm3, C/l, and µC/m³ are normalized so forms can pass short codes or spelled names. Every request multiplies the input value by the exact coulombs-per-cubic-metre factor for the source unit, then divides by the 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 charge clouds or polarity in plasma and beam work; 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, quantity, and rho 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 c_per_m3 quantity in coulombs per cubic metre, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag volume_charge_density_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. Microcoulomb-scale beam results and coulomb-per-cubic-metre textbook results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a materials LIMS, plasma-process controller, fusion diagnostics log, physics homework checker, or electromagnetic simulation plugin must convert volume charge density 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 surface charge density or force tools when a product pipeline needs several electromagnetic measure families, or call it alone when search traffic is specifically for volume charge density conversion—coulombs per cubic metre, litre, centimetre, millimetre, inch, and foot, plus milli, micro, and nano prefixes—rather than a general unit switchboard.
Integration use cases
Process and simulation pipelines
Automate volume charge density unit normalization in LIMS and EM solvers via a prepaid, deterministic API instead of ad-hoc spreadsheet factors.
Technical questions
Which volume charge density units are supported?
C/m3, C/cm3, C/mm3, C/L, C/in3, C/ft3, mC/m3, uC/m3 (µC/m3), nC/m3, and uC/cm3 (µC/cm3), plus common spelled aliases. Unknown names return invalid_input.