Angstrom to nm converter
5,890 Å, the sodium line from flame tests, is 589 nm. This converter divides any wavelength in angstroms by exactly 10, so older spectroscopy tables line up with the nanometres on laser and LED datasheets. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Angstroms
- 10
- Result
- 1 nm
- Converted
- 1
- Nanometers
- 1
- Nm
- 1
An angstrom-to-nanometre converter turns a spectroscopic wavelength listed in ångströms into the nanometre scale used by lasers, LEDs, and modern instrument software. Approximate mental shortcuts are unnecessary: the SI metre definition already makes one angstrom equal to one tenth of a nanometre exactly.
Why angstroms and nanometres still meet at a factor of ten
The angstrom, written Å, is a length equal to ten to the minus ten metres. Spectroscopists adopted it more than a century ago because visible emission and absorption lines fall in the thousands of angstroms, which are convenient four-digit integers on a photographic plate. The nanometre is ten to the minus nine metres, the SI-derived unit that now dominates laser catalogues, LED peak wavelengths, thin-film coatings, and most modern spectrometer software.
Because ten to the minus nine divided by ten to the minus ten equals ten, one nanometre is exactly ten angstroms, so converting a wavelength from angstroms to nanometres is a single exact division by ten. There is no survey factor, no temperature correction, and no tabulated physical constant to look up: the ratio is a pure power-of-ten identity from the metre.
Laboratory tables still print Balmer lines, the sodium D pair, and mercury calibration peaks in angstroms, while a laser-diode data sheet lists the same colour in nanometres; this converter is the dedicated landing for that unit change. Teachers sometimes say drop a zero as a mental shortcut, which matches dividing by ten when the number already has a trailing zero, but it is easy to misplace the decimal on a four-digit line such as six thousand five hundred sixty-three angstroms.
Practical tips, spectroscopy checks, and related searches
Prefer sending bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit suffixes, thousand separators, or the ångström symbol glued onto the digits. Round-trip sanity checks are easy: convert a known textbook value such as ten angstroms and confirm you receive exactly one nanometre after rounding, or convert five thousand eight hundred ninety angstroms and confirm five hundred eighty-nine nanometres, a sodium D neighbourhood often used in flame tests.
When teaching, pair the exact divide-by-ten path with the drop-a-zero shortcut so students see that the shortcut only works when the last digit is already a zero. Stay inside the absolute range so the division cannot overflow into a non-finite result the solver must reject. This landing targets people searching for angstrom to nm, convert angstroms to nanometers, or an Å to nm calculator; it is not a general multi-unit length hub, not a nanometres-to-angstroms primary form, and not a photon-energy converter that also emits electronvolts or terahertz.
Prefer this capability when the input is already in angstroms and you only need nanometres; if you must convert among many spectroscopic units in one call, use a broader photon or wavelength converter instead.
What you can do with it
Spectroscopy tables to instrument software
Export line lists printed in angstroms into nanometre fields on modern spectrometers, laser catalogues, and lab information systems with the same exact divide-by-ten factor every row.
Homework and lab-report checks
Students convert classroom Balmer and alkali emission lines from angstroms to nanometres and compare hand work against deterministic steps before submitting worksheets.
LED, laser, and coating data sheets
Optical engineers turn historic Å peak wavelengths into nm for vendor quotes, coating stacks, and photometric plots that expect the SI-derived nanometre.
FAQ
Is the factor ten exact or approximate?
Exact. This tool uses the SI length identity, not a survey factor or a rough drop-a-zero estimate that can misplace the decimal.
Can I convert nanometres back to angstroms?
This capability is angstroms → nanometres only. Multiply nanometres by ten on your side, or use a bidirectional length converter for other units.
Is the angstrom to nm converter free?
The browser tool is free and runs locally.
What is the sodium line of 5,890 Å in nanometres?
It is 589 nm. Dividing by 10 is all it takes, because one nanometre is exactly ten angstroms. The same step turns the hydrogen H-alpha line near 6,562.8 Å into 656.28 nm.
Why do some tables still list wavelengths in angstroms?
Spectroscopists adopted the angstrom more than a century ago because visible lines fall in the thousands of angstroms, handy four-digit numbers on a photographic plate. Laser and LED datasheets now use nanometres instead.
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/angstrom-to-nm-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"angstroms":10}'const res = await fetch("https://api.kit.forhosting.com/conv/angstrom-to-nm-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"angstroms": 10
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/angstrom-to-nm-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"angstroms": 10
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/angstrom-to-nm-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"angstroms":10}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"angstroms":10}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/angstrom-to-nm-conversion", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"angstroms": 10
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.angstrom_to_nm_conversion",
"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.
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
Invalid or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
Absolute values must stay within the published limit of one trillion. Classic classroom checks include ten angstroms mapping to one nanometre, one angstrom mapping to one tenth of a nanometre, and the hydrogen H-alpha rest wavelength near six thousand five hundred sixty-two point eight angstroms mapping to six hundred fifty-six point two eight nanometres. Send a JSON body with one required finite number field named angstroms. Aliases angstrom, A, value, wavelength, and angstrom_value are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes the rounded angstroms input, sets nanometers, nm, result, and converted to the same rounded nanometre magnitude, unit to the token nm, from_unit to angstrom and to_unit to nm, factor to the rounded reciprocal one tenth, angstroms_per_nm to the exact constant ten, formula to the string nm equals angstroms divided by ten, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.
Practical tips, spectroscopy checks, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit angstroms or pass text.
Technical questions
What formula converts angstroms to nanometres?
Nanometres = angstroms ÷ 10. One nanometre is defined as exactly ten angstroms because 1 Å = 10⁻¹⁰ m and 1 nm = 10⁻⁹ m.
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing angstroms field). Failed tasks are not charged.