ForHosting KIT · Unit converters

Electric flux converter

One statvolt centimetre equals 2.99792458 volt metres. Convert electric flux between V·m, N·m²/C, kilovolt and millivolt metres, C/ε₀ and statV·cm, for Gauss-law homework and checks between SI and Gaussian textbooks. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Worked example

If you enter

Value: 1
From: V·m
To: statV·cm

You get

Result: 0.3335640952 statV·cm
Converted: 0.3335640952
Value vm: 1
Factor: 0.3335640952

An electric flux converter turns one electric-flux magnitude into another common electrostatics unit without spreadsheet constants or hand-written Gaussian tables. Enter a finite value plus a source unit and a target unit among volt metres, newton square metres per coulomb, kilovolt and millivolt metres, coulombs per vacuum permittivity, and statvolt centimetres; the tool returns the converted flux, the SI intermediate in V·m, the exact unit factor applied, and step-by-step substitution lines you can paste into a lab notebook, homework set, or simulation note. Physics students converting Gauss-law homework, engineers comparing SI and esu textbook values, authors mapping enclosed-charge flux to C/ε₀, and firmware authors checking unit strings all need the same deterministic path.

Which electric flux units are supported and how conversion works

This capability converts among six everyday electric-flux units that dominate introductory electrostatics, SI laboratory work, and Gaussian/esu textbook problems. The volt metre (V·m) is the SI coherent unit of electric flux and the internal hub: every conversion multiplies the input by how many V·m equal one source unit, then divides by how many V·m equal one target unit.

Newton square metres per coulomb (N·m²/C) share an exact SI identity with volt metres, so their mutual factor is one and either label may be used as a display preference without changing the numeric magnitude. Kilovolt metres and millivolt metres use the exact SI kilo and milli prefixes of one thousand and one thousandth of a V·m respectively.

Coulombs per epsilon (C/ε₀) follows the Gauss-law convention that a flux equal to Q over ε₀ for Q in coulombs is reported in that unit; the implementation freezes CODATA 2018 vacuum permittivity so 1 C/ε₀ maps to a fixed multiple of V·m every run. Statvolt centimetres use the fixed c-linked Gaussian factor that makes one statV·cm equal 2.99792458 V·m, matching the usual esu conversion chain for potential and length. Same-unit requests succeed and return the input magnitude with a short message that no change of unit was required.

What you can do with it

Gauss-law homework in mixed units

Students convert V·m, N·m²/C, and C/ε₀ homework values with deterministic steps they can compare against hand calculations before submission.

SI versus Gaussian textbook checks

Instructors and authors convert SI volt metres into statvolt centimetres so esu worked examples match SI lecture notes without drifting c factors.

FAQ

Are V·m and N·m²/C the same?

Yes in SI: one N·m²/C equals one V·m exactly. The converter keeps both labels so you can match textbook notation without changing the number.

Is the electric flux converter free?

The browser tool is free and runs locally.

Does this convert electric field or magnetic flux?

No. It only converts electric flux among the six supported units. Electric field strength (V/m) and magnetic flux (Wb, Mx) are different quantities.

What does the unit C/ε₀ mean?

It comes from Gauss's law: the flux through a closed surface equals the enclosed charge divided by the vacuum permittivity. The permittivity is fixed from CODATA 2018 values, so 1 C/ε₀ always maps to the same number of volt metres.

Can I enter a negative flux?

Yes. A negative value keeps its sign for directed-flux work, such as flux leaving rather than entering a surface, and it is scaled exactly like a positive one.

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

POSThttps://api.kit.forhosting.com/conv/electric-flux

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-flux \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"value":1,"from":"V·m","to":"statV·cm"}'

const res = await fetch("https://api.kit.forhosting.com/conv/electric-flux", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "value": 1,
    "from": "V·m",
    "to": "statV·cm"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/conv/electric-flux",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "value": 1,
    "from": "V·m",
    "to": "statV·cm"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/electric-flux", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"value":1,"from":"V·m","to":"statV·cm"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"value":1,"from":"V·m","to":"statV·cm"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/electric-flux", 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": "V·m",
  "to": "statV·cm"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "conv.electric_flux",
  "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

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_abs 1000000000000

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

Unknown unit names fail with a clear invalid_input error instead of silent wrong factors.

Which electric flux units are supported and how conversion works

Common aliases are accepted case-insensitively: volt meters, N m2/C, kilovolt metre, millivolt meters, coulombs per epsilon, statvolt centimeters, and related slash or word forms. If the name is not on that list the solver rejects the request with invalid_input naming the bad field and listing supported units, so clients never guess whether a typo produced a wrong number. Negative flux values are allowed for signed directed-flux contexts; absolute input magnitude must stay within the published one-trillion limit so intermediate products remain finite in IEEE double precision on the Worker and in the browser. This tool deliberately stays on the electric-flux axis: it does not convert electric field strength (V/m), pure voltage prefixes, magnetic flux (weber or maxwell), or charge alone without the ε₀ flux convention.

How to call the API and read the response

Value must be a finite number or a strict numeric string within absolute limits of one trillion. Wire this into dashboards, mobile clients, or batch jobs that already hold an electric-flux reading and only need a second unit for display, homework checking, or SI versus esu comparison without shipping floating conversion tables in every app binary. Prefer bare numbers for value when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without currency symbols or thousand separators. Send a JSON body with three required fields: value (aliases flux, amount, phi, and phi_e), from (aliases from_unit, unit_from, and source), and to (aliases to_unit, unit_to, and target). From and to must resolve to supported unit names after alias normalization. On success the response echoes the rounded input value, canonical from and to labels, result and converted set to the same rounded target magnitude, value_vm as the SI intermediate in volt metres, unit as the target label, factor as the from-to multiplier, formula as the short equation string, message as an English summary, steps as ordered substitution lines, and supported_units as the six canonical identifiers. Failed validation—missing fields, non-finite numbers, values outside absolute limits, or an unknown unit name—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.

Practical tips, limits, and when to use this landing

Round-trip checks are straightforward: convert A to B and B back to A and confirm you recover the original within the published twelve-decimal rounding. Conversions that touch C/ε₀ produce large or tiny intermediates by design; stay inside the published result magnitude cap so extreme inputs do not overflow. This landing targets people searching for an electric flux converter, volt meters to statvolt centimeters, N m2/C to V m, or coulombs per epsilon online; it is not a general multi-quantity unit converter, not an electric field strength tool in V/m alone, not a magnetic flux weber converter, and not a charge-only calculator. Prefer this capability when both endpoints are among the six supported electric-flux units and you need deterministic factors and step strings; if you need field strength in V/m or force from charge and field, use a dedicated electric-field capability instead. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when clients deliberately probe unknown unit names before wiring production clients.

Integration use cases

Lab notes and simulation post-processing

Engineers convert kV·m or mV·m flux-scale outputs into SI V·m for reports, dashboards, and cross-tool validation of electrostatic solvers.

Technical questions

Which electric flux units can I convert?

Volt metres (V·m), newton square metres per coulomb (N·m²/C), kilovolt metres (kV·m), millivolt metres (mV·m), coulombs per epsilon (C/ε₀), and statvolt centimetres (statV·cm), including common full-word aliases.

What happens if I send an unknown unit name?

The API returns invalid_input, names the bad field, and lists the supported units. The failed task is not charged.

Read the full KIT documentation →

Run — free

Worked example

Which electric flux units are supported and how conversion works

What you can do with it

Gauss-law homework in mixed units

SI versus Gaussian textbook checks

FAQ

Related tools

For developers — API access

API endpoint

Call it from your stack

Example request

Example response

Pricing

Limits

Errors

Technical notes

Which electric flux units are supported and how conversion works

How to call the API and read the response

Practical tips, limits, and when to use this landing

Integration use cases

Lab notes and simulation post-processing

Technical questions

thank you