Was a converter ever priced on its own — a bundled extra in 2001, a door to paid tiers today?

On the 2001 price page, the conversion had no price row at all. The page printed one product and one price, and the translator was named inside that same line as something included with the purchase — so the converter owned zero rows. Its own feature page then names every format it could read: 14 names, 16 variants, and neither STEP nor IGES is among them. A current converter page has moved the same question to the other end: the convert action sits beside four paid doors — a paid tier, a desktop application, a developer API and an agent endpoint. Here there are zero of both, one direction, one output, and the 10 mm cube still lands at 12 triangles and 684 bytes, where 684 = 84 + 50 × 12.

This page answers one question: whether the act of converting a CAD file has ever been priced as a thing in itself. The left half is read off dated public captures of a vendor’s own pages; the right half is re-measured from the bytes this site writes. Every figure below is reproduced by this project’s own test suite before release.

Zero rows of its own

The 2001 page is short enough to describe as a layout rather than as a claim. It carried a product name, a price, and directly beneath both, one sentence saying the translation program came with the purchase. There was no second line for the translator, no per-conversion counter, no option to buy the translation alone.

The consequence is economic rather than moral. A thing with no row of its own cannot be compared, budgeted or shopped for: a buyer in that year could ask what the machining program cost, and could ask whether the translation came inside it, but could not ask what a translation cost, because the page never named a number for one. A later capture of the same address, from 2006, no longer prints that price headline at all — the page had been reorganised around the machining product’s own trial, and this page says only what those two captures show.

That is the first half of the answer. Conversion was not a product line in 2001; it was a feature folded into the price of something else.

What the gift could read

The translator had a page of its own, and that page is the yardstick. Its first feature line lists every format it accepted, in one sentence, from drawing exchange formats through the 3D suites of that decade. Counting the names gives 14; counting the spellings gives 16, because two of those names were offered in two forms each — one as binary or text, one in two versions.

Neither STEP nor IGES appears anywhere on that list, and those are exactly the two formats this converter reads. So the bundled extra and the modern tool do not overlap at the one point that matters: the gift could not open the file a CAD user would most likely bring. Coverage is the only honest way to price a bundle — if the gift cannot read your format, its being free tells you nothing.

Four doors beside one button

The other end of the same history is not a price row either — it is a doorway. On a current converter page for STEP to STL, the conversion itself is still not priced. What is priced sits beside it: a paid tier, a desktop application, a developer API and an agent endpoint, four paid surfaces arranged around one free action. The page also carries privacy badges at the top, and a badge is a claim, not a list of what the page actually requests; the upload-safety page owns that comparison.

This is not a criticism of the arrangement, it is a description of the model. Free conversion next to paid surfaces is a funnel: the conversion answers the search, the doors convert the visit. Both the 2001 bundle and the modern funnel have the same property that matters here — the conversion itself is never the thing with the price tag. In 2001 it was folded into a machining program; today it is folded into a menu.

What this page counts instead

The output side is where the count becomes checkable. A binary STL is an 84-byte header plus 50 bytes per triangle, so the 10 mm test cube is 12 triangles and 684 bytes at Draft, Normal and Fine, and the 18-part assembly leaves as 7,372 triangles and 368,684 bytes at Normal from a 433,606-byte input, where 368,684 = 84 + 50 × 7,372.

Nothing in that chain is an offer. There is one input family spelled four ways, one output family, one setting ladder that changes the triangle count and never the terms, and no surface that can be bought. The accepted inputs and the single output are listed in one place only, the format section of the verification page.

Two facts about the captured pages, stated as facts and nothing more: the price headline appears in the March 2001 capture and is gone from the February 2006 one, and this page prints no amount from either. Neither capture says what a conversion should cost today, and this page does not infer one.

What you can check without trusting the page

• Count the rows on the old page. One product, one price, and the translator named inside that line. If a page has no row for a thing, that thing has no price to compare — the absence is the evidence.
• Count the names on the translator’s list. Fourteen names, sixteen spellings, and a search for STEP and IGES inside that list returns nothing. Coverage, not the word free, is what a bundle is worth.
• Count the doors on the current page. Four paid surfaces beside one free action. The number is countable in a minute and it is the whole pricing model.
• Check the bytes here. (bytes − 84) ÷ 50 returns the triangle count exactly: 684 bytes returns 12, and 368,684 bytes returns 7,372, with no rounding in either direction.

Questions this page answers

Has a converter ever been sold with a price of its own?

Not on that 2001 price page. It printed one product and one price, and the translator was named inside that same line as something included with the purchase, so the number of price rows belonging to the converter was zero. A reader could not compare the conversion against anything, because there was no row to compare. A later capture of the same page, from 2006, carries no price headline at all.

How many formats could that bundled translator read?

Fourteen names, sixteen variants: two of the names are written in two spellings each, one as binary or text and one in two versions. STEP and IGES are not on that list, and those are the two formats this site converts. So the gift was a translator that could not read the input a buyer of that era’s CAD files would most likely hand it, and the count is the honest measure of what the gift was worth in coverage.

What sits beside a convert button today, and what sits beside it here?

On a current converter page the convert action is placed beside four paid doors: a paid tier, a desktop application, a developer API and an agent endpoint. The conversion is not priced; it is the way into a menu that is. Here the count is zero accounts, zero tiers and zero doors, one direction and one output, and the 10 mm cube still lands at 12 triangles and 684 bytes, where 684 = 84 + 50 × 12.

Where these numbers come from

Published 2026-10-31 · Last updated 2026-10-31

• One product, one price, the translator included in that line, and a 2006 capture without the price headline — dated public captures of a vendor’s own pages, kept in this project’s research folder and read by the test suite before the page may print any of it; no sentence from those pages is reproduced here, and no amount from them is printed.
• 14 readable names, 16 spellings, no STEP, no IGES — counted by the test suite off the format list in the translator’s own capture, not estimated here.
• Four paid doors beside one convert action — a structural count taken from a current converter page on 29 October 2026; the page is described by what it offers, not by name.
• 12 triangles / 684 bytes for the 10 mm cube — this project’s own output for cube-10x10.stp at Draft, Normal and Fine, re-run by npm test.
• 433,606 bytes in, 7,372 triangles and 368,684 bytes out — the 18-part AP214 assembly as1-oc-214.stp at Normal, with the length asserted against 84 + 50 × 7,372.
• What this page does not print — no monthly search volume, no keyword bid, no competitor name, no amount from any capture, no capacity figure from another converter, and no byte counts from the captures themselves. Large assemblies are unverified.

npm test

The command above re-runs every number on this page. These are this page’s own test files and own settings, not a CAD standard. The price-list page owns which side of a price list STEP once sat on, the cloud-pricing page owns what an online service charged and when it stopped, and the format-pairs page owns the year a converter sold pairs of formats one at a time.

Sponsored link: Creality’s official store (3D printers, scanners, filament and parts) is an affiliate partner — clicking it may earn this site a commission. It changes nothing about the converter; see what sponsored links mean here.