Why is a free STEP to STL converter free — and who pays for the capacity, the wait and the ad blocker?

Someone is paying for the processors. A converter that tessellates on its own machines has a standing bill, and the three rules a reader meets on such a site are that bill cut three ways: a ceiling on how large one job may be, a queue that shows up as waiting, and advertising around the tool — which is why a page can honestly say that blocking ads reduces its limits. This converter never sends the file anywhere: 7,604,031 bytes of engine code arrive once per session and the work runs on your own processor, so the 10 mm cube is 12 triangles and 684 bytes at every setting and 684 = 84 + 50 × 12. The bill did not vanish; it moved to your machine, and this page says so instead of calling it free.

This page answers one question: not whether a converter is free, but who pays for it. The cost side is described from what such pages state about their own arrangement; the local side is this site’s own output, re-measured by the project’s test suite before release. No figure from another converter is printed here.

One bill, three faces

Read separately, a ceiling, a wait and an ad blocker look like three unrelated policies. They share one cause: processors and bandwidth cost money every hour, and the people running them have to recover it from somewhere. Once the tool itself is free to use, the recovery has to happen on the edges of the tool.

There is a second, quieter way to pay the same bill: run the job on the visitor’s hardware. That is the arrangement on this site, and it is the reason none of the three rules above exists here in the same form. There is no ceiling to publish because no server receives the file, no queue because nothing is shared, and no ad-blocker term because the controls do not depend on an advertisement being fetched.

Where the compute sits decides which rules exist

A converter can put the tessellation in one of two places, and the placement is the whole difference. On the server side, your file travels to machines you do not own; the operator sets a ceiling because the processor minutes are theirs, holds a queue because the queue is what lets them oversubscribe those minutes, and puts the tool beside advertising because the minutes have to be paid for. A converter that states it processes files on dedicated conversion servers has simply described that arrangement, and a statement that ads change the limits is the same arrangement seen from the front.

On the tab side, the tessellation runs on hardware you already bought, and the only thing that travels is code. Here that code is 7,604,031 bytes of WebAssembly, fetched from this site’s own directory once per session and then kept; the reader arrives at the format section for the list of what may be handed to it — STEP, STP, IGES and IGS in, STL out, one direction only. The bill still exists. It appears as processor time on your machine, not as a limit on someone else’s.

The tab’s bill, in numbers

“Local” does not mean free, and the honest way to show that is to print what the local job costs in work done. The flat cube is the floor: a 10 mm cube with twelve flat faces is 12 triangles and 684 bytes at Draft, Normal and Fine, because a flat face needs no more triangles however fine the setting gets. The 18-part assembly is the ceiling of what is verified here, and its bill grows with the setting.

The first row and the last row are the useful pair. Twelve triangles is what a flat part costs no matter what you ask for, and 21,116 triangles is what a curved assembly costs when you ask for the finest setting — a factor of over a thousand in work, on the same tab, with the same engine. That range is the local bill, and it is the reason a browser converter cannot promise that every model converts in the same instant. Every length above is 84 + 50 × its triangle count, so it can be checked with a calculator. These are this page’s own choices, not a CAD standard.

What an ad blocker changes, and what it cannot

A converter that states blocking ads reduces conversion limits, hides settings and lengthens processing and download times has answered the question for its own case: the permissions come from the page, so the page has to load. There is nothing contradictory about it. The arrangement is simply server-funded.

It cannot work that way here, and not because this site is nicer. The controls and the engine are all served from this site’s own directory, the tessellation happens in the tab, and no step of the conversion calls out to a page element. If the advertisement image on this page never arrives, the converter behaves exactly the same. The short answer to why an ad blocker changes a converter’s limits on the upload-safety page says the same thing in one paragraph; this page owns the arithmetic behind it.

Two things follow, and both are limits on this page rather than claims about anyone else. First, the site does carry a sponsored banner; it is a still image and a link, and it is not in the path of the conversion, which is why removing it changes nothing about what the tool will do. Second, a local bill cannot be recharged by anyone but the reader, so when a model is too heavy for a tab the honest outcome is a slow tab, not a paid upgrade that makes it faster.

The one-minute check anyone can run

Open the converter, press the browser’s network panel, and convert a file while watching the requests. Two outcomes tell the two arrangements apart without trusting either page.

• If a request carries the file’s bytes, the bill is on someone else’s machines, and the ceiling, the queue and the ad terms are that bill being recovered.
• If no request carries the bytes, the file stayed where it was and the work happened on the machine in front of you — which is what this site does. The only sizeable arrival is the engine itself, 7,604,031 bytes, once per session.
• Then measure the artifact. For a binary STL, (bytes − 84) ÷ 50 returns the triangle count, so 684 bytes returns 12 and 368,684 bytes returns 7,372 without rounding in either direction.

The two checks answer different questions: the network panel says who paid for the compute, and the length says whether the compute happened at all. A page can be free to visit and still expensive to run; this one names the expense instead of hiding it behind the word free.

Questions this page answers

Why can an online STEP to STL converter be free at all?

Because the bill is paid somewhere other than the upload box. A service that tessellates on its own machines pays for processors, cooling and bandwidth, and it recovers that cost through a file-size ceiling that keeps any single job predictable, a queue that lets the same machines serve more people, and advertising on the pages around the tool. The tool stays free to use; the compute is not free to run.

Why does an ad blocker change what a converter lets me do?

If a converter states that blocking ads reduces conversion limits, hides some settings and makes processing and downloads slower, then the limit is not a technical property of your file. It is a term of the payment arrangement: the page around the tool is part of how the server time is funded, so removing the funding removes part of the service. A converter that runs the job in your own tab has no such term, because nothing in its controls waits for an advertisement.

Does that make a browser converter cost nothing to run?

No, and this page will not say so. The bill moves to your machine: 7,604,031 bytes of engine code arrive once per session, and the tessellation runs on your processor, using your electricity and your time. The bill is visible in the triangle counts, which rise from 4,900 at Draft to 21,116 at Fine on the 18-part assembly, while the flat 10 mm cube stays at 12 triangles and 684 bytes at every setting. Large assemblies are unverified.

Where these numbers come from

Published 2026-10-29 · Last updated 2026-10-29

• The server arrangement, and the ad-blocker term — described from what a converter that runs its own conversion servers states about its own pages; this page repeats the arrangement in its own words, prints none of that site’s capacity or retention figures, and names no competitor.
• 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, 4,900 / 7,372 / 21,116 triangles and 245,084 / 368,684 / 1,055,884 bytes out — the 18-part AP214 assembly as1-oc-214.stp at the three shipped settings; each length is asserted against 84 + 50 × its triangle count.
• 7,604,031 bytes of engine code — the size of the shipped WebAssembly kernel on disk, asserted against the page’s own figure, fetched once per session from this site’s own directory.
• What this page does not print — no monthly search volume, no keyword bid, no competitor name, no price from another product, and no capacity, batch or retention figure from another converter. None of the archived page’s sentences is reproduced here.

npm test

The command above re-runs every number on this page. The size-limit page owns the ceiling question, the pipeline page owns what happens to the geometry inside a converter, the upload-safety page owns where a file goes, and the format section is the single authority for what is accepted and what is written.

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.