Sieve mesh size converter
Read any sieve callout as a real opening and back: 100 US mesh is a 150 µm opening, or 0.15 mm, so lab sieve stacks, supplier sheets and particle-size specs describe the same screen. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 100
- Source unit
- us_mesh
- Target unit
- micron
- Result
- 150
- From label
- US Standard mesh (ASTM E11)
- To label
- micrometres (opening)
- Micron
- 150
A sieve mesh size converter turns a US Standard mesh number, a Tyler Standard Screen Scale designation, or a clear opening written in micrometres, millimetres, or inches into any other unit in that set without hunting printed sieve charts or rebuilding spreadsheet factors.
Supported units, mesh tables, and how conversion works
When the source is a mesh number, the engine looks up the published nominal square-opening size in micrometres for that number in the matching series table, then scales to the target unit with exact factors: one millimetre equals one thousand micrometres, and one inch equals twenty-five point four millimetres exactly. When both ends are linear opening units, the path multiplies by the micrometres-per-unit factor for the source and divides by the factor for the target.
Because linear routes share one micrometre intermediate, 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. Wire diameter, percent open area, and non-square weave geometries are intentionally out of scope so particle-size and sieve users get predictable opening-size results under one clear convention.
Mesh conversions in the lab and on the plant floor
Use the free in-browser sieve mesh size converter when you need a quick US mesh to micron, Tyler mesh to millimetre, or micron to nearest mesh check while reading a particle-size specification, a sieve stack label, or a supplier data sheet. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a particle-size 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, formula, and intermediate micron or millimetre fields directly into cards that show both the number and the conversion path sieve analysts expect on paper.
What you can do with it
Lab sieve stacks and particle specs
Convert US or Tyler mesh callouts to micron or millimetre openings so protocols, certificates, and LIMS records share one opening size without hand charts.
Mineral processing and abrasives catalogs
Normalize mixed mesh and metric opening fields so inventory, product pages, and process models compare screens consistently.
FAQ
How do I convert 100 US mesh to microns?
The response result is the nominal ASTM E11 opening in micrometres (150 for mesh 100).
What is the difference between US mesh and Tyler mesh?
US mesh follows ASTM E11 designations; Tyler mesh follows the historical Standard Screen Scale. The same mesh number can have a slightly different opening, so the converter uses separate tables and converts through micrometre opening size.
Is the sieve mesh size converter free?
The browser tool runs free on your device.
Can I find the mesh number from an opening size?
Yes. Enter the opening in microns, millimetres or inches and choose US or Tyler mesh as the target. The converter returns the nearest tabulated mesh number, so slightly rounded lab measurements still resolve.
Does it account for wire diameter or open area?
No. It converts the clear square opening only. Wire diameter, percent open area and non-square weaves are outside its scope, so check those figures with the screen supplier.
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/sieve-mesh \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":100,"from":"us_mesh","to":"micron"}'const res = await fetch("https://api.kit.forhosting.com/conv/sieve-mesh", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 100,
"from": "us_mesh",
"to": "micron"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/sieve-mesh",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 100,
"from": "us_mesh",
"to": "micron"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/sieve-mesh", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":100,"from":"us_mesh","to":"micron"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":100,"from":"us_mesh","to":"micron"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/sieve-mesh", 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": 100,
"from": "us_mesh",
"to": "micron"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.sieve_mesh",
"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, mesh tables, and how conversion works
The converter accepts five families under stable canonical codes: us_mesh for US Standard sieve designations aligned with ASTM E11, tyler_mesh for the historical Tyler Standard Screen Scale, micron for opening size in micrometres, mm for millimetres, and in for inches of clear opening. Friendly aliases such as us, astm, mesh, tyler, um, µm, micron, millimetre, and inch are normalized case-insensitively so forms and APIs can pass either short codes or full names. When the target is us_mesh or tyler_mesh, opening size is converted to micrometres and the nearest tabulated mesh number is returned so slightly rounded lab measurements still resolve to a useful screen label.
Request shape, response fields, and unknown-unit or mesh errors
The error message names the bad field and lists the supported set or the tabulated mesh numbers so clients can correct forms without guessing. 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, mesh, and size 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, intermediate micron, mm, and inches fields, an optional dimensionless factor when the path is linear or mesh-to-opening, a short formula line suitable for UI display, the method tag sieve_mesh_opening, mesh_tables identifiers for the US and Tyler series, and the list of units_supported. When converting to a mesh series the payload also includes nearest_mesh, table_um, and delta_um so you can see how far the input sits from the published table opening. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, any token that does not map to a supported unit, mesh numbers not present in the selected table, and non-positive openings when converting to mesh 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 table lookup and arithmetic with no randomness, no remote catalog, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests.
Browser use, API pricing, and lab or process workflows
Switch to the prepaid API when a materials lab LIMS, mineral-processing pipeline, powder-coat or abrasive catalog, pharmaceutical sieve protocol, or quality-control system must convert mixed mesh and metric openings 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 length or mass converters when a sample preparation workflow needs several measure families, or call it alone when search traffic is specifically for sieve mesh size conversion—US mesh, Tyler mesh, and micron opening—rather than a general unit switchboard.
Integration use cases
QA and purchasing pipelines
Call a prepaid, deterministic sieve mesh API from inspection tools and purchase orders with clear invalid_input on unknown units.
Technical questions
What happens if I pass an unknown unit?
The request fails with invalid_input. The message names the field and lists supported units (us_mesh, tyler_mesh, micron, mm, in). Validation failures are not charged.
How is nearest mesh chosen from a micron opening?
Opening size is converted to micrometres, then the tabulated mesh whose nominal opening is closest is returned, with table_um and delta_um so you can see the residual.