EMC field strength converter

The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when compliance pipelines need the same contract from servers and automation.

Supported units and how the conversion is computed

Friendly aliases such as volts per meter, microvolts per meter, decibel microvolts per meter, amperes per meter, and short codes with spaces, slashes, or underscores are normalized case-insensitively so forms and APIs can pass either short codes or full names. Every request first maps the input into an intermediate volts-per-meter magnitude: linear E units multiply by exact decade factors, log E units invert twenty times log base ten against the unit’s reference scale, and H units multiply by free-space impedance Z0 equal to μ0 times c with μ0 taken as the exact conventional four-pi times ten to the minus seven henry per meter and c equal to two hundred ninety-nine million seven hundred ninety-two thousand four hundred fifty-eight meters per second.

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. Linear-to-linear pairs allow signed values when you need a signed E or H direction in analysis pipelines. 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 level 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 volts_per_meter quantity, the free-space-equivalent amperes_per_meter, the free_space_z0_ohm constant used for E-to-H links, a short formula line suitable for UI display, the method tag emc_field_strength_si_freespace, 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. Converting into a logarithmic unit requires a positive linear magnitude; zero or negative intermediate field strength in V/m raises invalid_input because twenty-log-ten is undefined for non-positive field. 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. Microvolt-per-meter lab floors and kilovolt-per-meter stress levels 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 EMC workflows

Switch to the prepaid API when a test-lab LIMS, pre-compliance scanner, report generator, RF monitoring dashboard, curriculum checker, or instrumentation pipeline must convert field strength 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, power, or antenna tools when a product pipeline needs several RF measure families, or call it alone when search traffic is specifically for electromagnetic field strength conversion—V/m, dBuV/m, and A/m—rather than a general unit switchboard.