Is a converter's resolution setting a triangle count or a file cap — and what does the same knob hide when it prints both?

A quality control can print the mesh density it will give you, or the largest file it will take, and those two numbers move in opposite directions. On a server they are the same cost, so one knob often carries both: turn it toward finer geometry and the upload ceiling falls while the triangle count rises. That means the label alone cannot tell you which quantity you just chose — the direction can. Here there is nothing to upload, so the same three stops hold only the triangle side: the flat 10 mm cube is 12 triangles and 684 bytes at Draft, Normal and Fine, a rounded cube runs 40 / 56 / 140, and a cone runs 286 / 516 / 2,142, where 684 = 84 + 50 × 12.

This page answers one question: when a converter labels its resolution control, which quantity is that label naming. The tool page on the other side was read on 31 October 2026 and is described by structure only — no name, no stop value and no sentence from it is reproduced here. The measured side is this site’s own output, re-run by this project’s test suite before release.

What the knob prints

Start with the control itself, because that is all a converter page usually gives you. The page read for this article offers exactly one setting: a three-stop resolution selector. Each stop is named after the largest file the service will accept at that stop. Nothing beside it names a triangle count, a chord deviation, an angular tolerance or a unit. There is no second control for quality, and no table that maps a stop to a number of triangles.

The same page also calls itself browser-based, in the same breath as a flow that uploads a file and converts it elsewhere. Both statements are true at once: the interface runs in the browser, and the geometry is processed on the service’s machines. So the word "browser-based" describes where the buttons live, not where the mesh is made — which matters here, because the machine that makes the mesh is the machine the knob is protecting.

A label is not decoration; it is the only thing the operator chose to tell you. When the only number printed beside a quality control is a file size, the page has answered a question about its own capacity rather than about your model.

Three stops, one kind of number. The selector read for this article names each stop after its upload ceiling and prints nothing about triangles, deviation or units, so the mesh decision is taken somewhere the reader cannot see.

Two quantities under one label

A quality control is usually expected to answer "how good will the mesh be". A capacity control answers "how much can I send". Those are different desires held by different people: the reader wants the first, and the operator of the server is paying for the second. When a page prints only one of the two, it has chosen which desire to answer.

What makes the fusion interesting is that the two quantities cannot share a scale. Push a setting toward finer geometry and the triangle count goes up, while the amount of work per upload also goes up — so the largest file the machine can afford to accept goes down. One knob moved one way therefore moves one number up and the other down, and any single label placed beside it has to pick a side.

That is the whole trap, and it is not a trick of wording: the two stop orders really are reversed. A stop that says "better" to a reader says "smaller input" to an operator. On the page read for this article the sides are resolved the operator’s way, and the reader is left to guess what the stop does to the mesh.

One knob, two opposite rankings. A cap shortens as the setting refines while a triangle count lengthens; the numbers on the right are this site’s measured rounded-cube and cone counts, so the reversal can be seen on a real scale.

How to read the direction

There is a one-second test that needs no inside knowledge. Look at the number beside the control and ask which way it moves when the setting is turned toward finer geometry. If it falls, it is a ceiling on what you may send. If it rises, it is a count of what you will get. A label in a size unit can only be the first kind; a bare integer can be either, which is why the direction is the safer test.

Three labels a quality control can carry, ranked by what they move
What the label counts	As the setting refines	What it bounds
triangles	rises	the mesh you receive
file size	falls	the upload the service accepts
chord deviation	falls	the distance between surface and triangle

Two of the three fall. That is why a falling number is not evidence of a quality setting at all — a deviation and a ceiling both shrink as the geometry is refined, and only the triangle count grows. A page that prints a shrinking number and calls it resolution has labelled one of two falling quantities and left the other one, plus the mesh itself, unmentioned.

The second test is the geometry that cannot be refined. A flat face is the same twelve triangles whether the setting is coarse or fine; only a curved surface changes. Convert a cube at every stop and compare the counts: on this site the flat 10 mm cube is 12 triangles and 684 bytes at Draft, Normal and Fine, while a cone on the same page runs 286 / 516 / 2,142. A setting that moves the cone and not the cube is a tessellation budget; a setting whose number never describes triangles at all is a cap.

The same knob without a server

Take the upload away and the knob loses half its job. There is no file arriving at a machine that has to be protected, so there is no ceiling to print, and the remaining quantity is the mesh. On this site the three stops are exactly that: a triangle budget applied by the OpenCASCADE kernel inside the tab, with the numbers measured rather than chosen for display.

The measurements sort the geometry the way the test above predicts. A flat cube does not move at all: 12 triangles and 684 bytes at all three stops, because 684 = 84 + 50 × 12 and there is nothing on a plane to subdivide. A rounded cube moves modestly, 40 / 56 / 140, because only its fillets are curved. A cone moves most, 286 / 516 / 2,142, because its lateral surface is curved everywhere. The deviation bound behind those stops is 0.02, 0.005 and 0.001 mm of linear deflection, which is a surface-error number and not a capacity number.

That is what a label in triangles buys you: the ability to predict the output before you run it. In a tab, a 433,606-byte 18-part assembly at Normal comes out as 7,372 triangles and 368,684 bytes, where 368,684 = 84 + 50 × 7,372, and no stop had to be traded against a ceiling to get there.

Curvature is what the knob moves. The cone climbs from 286 to 2,142 triangles across the three stops while the flat cube holds 12 triangles and 684 bytes, so the setting is a budget on curved surface and not a cap on anything.

Why the two were fused

The fusion has a cause, and it is the same cause that decides where the work runs. A server pays for the conversion in machine time and bandwidth, and both of those grow with a larger upload and with finer geometry. So the operator’s cheapest protection is a single control that limits the pair. The label printed beside it is then the quantity the operator is guarding, because that is the number that appears on the bill.

You can see the logic in the shape of the page: one selector, three stops, and no second control anywhere. If a page wanted to let you choose mesh density independently, it would have to expose a deviation or a triangle count and pay for both at the top stop. Offering one dial that only turns the capacity down is cheaper than offering two that can both be pushed up.

In a tab the bill is your own processor time, so the pair splits: the cap disappears and the density stays. That is why this site can print the counts above as a promise — the answer to "what will I get" is the only thing left on the knob. It is also why the honest reading of a size-labelled knob is not "coarse versus fine" but "how much may I send".

What you can check in a minute

Read the direction, not the label. Turn the control toward finer geometry and watch the printed number. Falling means a ceiling on your upload; rising means a count of your mesh.
Look for a second control. A page that offers only one selector has fused the two quantities. If there is no deviation, no triangle count and no unit anywhere on the page, the mesh decision was taken off-screen.
Convert a flat cube at every stop. A plane has nothing to refine, so the count must not move: here it is 12 triangles and 684 bytes at all three stops. If the number beside the knob changes while the cube does not, that number is not a triangle count.
Weigh the output. (bytes − 84) ÷ 50 returns the triangle count exactly: 684 bytes gives 12, and 368,684 bytes gives 7,372. This is the only line on this page you can run without trusting anybody.

Questions this page answers

If a converter labels its quality setting as a file size, what am I actually choosing?

You are choosing an upload ceiling, not a mesh density. The label bounds how large a file the service will accept at that stop; the triangle count behind it is set by whatever tessellation the service runs, and that number is not on the control. On the page read for this article the three stops were labelled only by the largest file each would take, with no triangle count, no chord deviation and no unit beside them.

How can I tell whether a quality setting is a triangle count or a file cap?

Read the direction. Refinement moves a triangle count up and a file cap down, so if the number beside the knob falls as the setting gets better, it is bounding your upload and not your mesh. The second test is the flat cube: here it returns 12 triangles and 684 bytes at Draft, Normal and Fine alike, because a flat face has nothing to refine; the cone on the same page runs 286 to 2,142.

Why would a converter put a file cap and a quality setting on the same knob?

Because on a server both of them are the same cost. A larger upload and a finer mesh each take more machine time, so the operator needs one control that limits both, and the label that survives is the one the operator pays for. In a tab there is no upload to bound, so the knob is left holding only the triangle budget, which is why the answer here can be printed as a count.

Where these numbers come from

Published 2026-11-02 · Last updated 2026-11-02

A resolution selector whose stops are labelled only by upload ceiling — a structural reading of one converter’s tool page, taken on 31 October 2026 and again on 31 October 2026 before it was archived; the page is described by what it offers, not by name, and no stop value from it is printed here.
“Browser-based” placed beside an upload-and-convert flow — the same dated reading; the phrase is treated as a statement about the interface, not about where the geometry is processed.
12 triangles / 684 bytes for the flat 10 mm cube — this project’s own output for cube-10x10.stp at Draft, Normal and Fine, re-run by npm test.
40 / 56 / 140 triangles for the rounded cube, 286 / 516 / 2,142 for the cone — the site’s own test files at the three shipped presets, with 0.02, 0.005 and 0.001 mm of linear deflection; the byte counts follow 84 + 50 × triangles.
433,606 bytes in, 7,372 triangles and 368,684 bytes out — the 18-part AP214 assembly at Normal, with the length asserted against 84 + 50 × 7,372. Large assemblies are unverified.
What this page does not print — no stop value from another converter’s selector, no competitor name, no monthly search volume, no keyword bid. These are this page’s own test files and own settings, not a CAD standard.

npm test

The command above re-runs every number on this page. The triangle-budget page owns choosing a count by curvature, the size-limit page owns the upload ceiling itself, and the workflow page owns where the quality step sits in the procedure.