A Pipeline Note: The Generator Hands Off GLB, and STL↔OBJ Is a Local Conversion Step

A generation session and a format conversion are easy to flatten into one "export" step. They are not the same contract. On the live pages of 3DMaker, the AI generator's visible handoff is a GLB file plus a rendered preview image. STL and OBJ show up later, as a separate, in-browser conversion step for print and CAD interchange — and the converter pages say the file never leaves the device.

The generator contract: a textured mesh, handed off as GLB

The homepage document title is 3DMaker — AI 3D Model Generator | Text & Image to 3D. The heading is 3DMaker: The AI 3D Model Maker for Any Idea. The lead describes an AI 3D model generator that turns a prompt or a photo int
o a textured, game-ready mesh, and the page uses "free to try" as marketing language — that wording is not a measurement.

Use cases listed on that page include game props, product prototypes, printable parts, and pitch-deck prototypes, along with characters, vehicles, architecture, furniture, and gadgets. A "3D print part" example is included, and gallery models can be dragged to rotate. There are two ways to start — a written prompt (up to 1,024 characters, with four mesh density levels from Fast to Ultra) or a photo (a single image, or up to four angles, with PBR taken from the source photo). Those input modes are not the subject of this note; they only explain how a mesh arrives.

The visible export contract, stated in the FAQ "What file formats can I export my 3D models in?", is narrower than a print-shop wishlist. This 3D model maker exports GLB and a rendered preview image out of the box, ready for Blender, Unity, Unreal Engine, Three.js, Babylon.js, or model-viewer. PBR textures are included. Other format names that appear only in social-preview text are not treated here as an on-page generator export. The generator itself is not documented on that page as an STL or OBJ exporter.

Why STL and OBJ still matter after a GLB handoff

Printable parts are listed as a use case, so interchange with print and CAD tools still comes up after the GLB leaves the generator. The formats themselves are older than this product, and the facts below come from the Library of Congress, not from product marketing.

The Library of Congress's Sustainability of Digital Formats entry for the STL (STereoLithography) File Format Family describes STL as an openly documented format for describing the surface of an object as a triangular mesh (triangular facets). It is also referred to as "Standard Triangle Language" and "Standard Tessellation Language." It was developed initially for stereolithography, a form of 3D printing used in the late 1980s for rapid prototyping, and was first documented in the StereoLithography Interface Specification in 1988 by 3D Systems, Inc. There are two subtypes, ASCII and binary; binary is more common because it is more compact. Each triangular facet stores vertex coordinates and a unit normal pointing outwards. There is no standard support within STL for colors or textures. The LoC page quotes: "This format describes only the surface geometry of a three-dimensional object without any representation of color, texture or other common model attributes." STL is still often described as a de facto standard for 3D printing and rapid prototyping; its strengths are simplicity and independence from a particular 3D software package or rapid prototyping method. The LoC Recommended Formats Statement also includes STL as an acceptable format for scanned 3D objects (photogrammetry output).

The companion entry for the Wavefront OBJ File Format describes a format for defining the 3D geometry for the surface of one or more objects. It was first used by Wavefront Technologies around 1990; a specification was published to encourage interoperability. The specification introduction stated: "Object files define the geometry and other properties for objects in Wavefront's Advanced Visualizer. Object files can also be used to transfer geometric data back and forth between the Advanced Visualizer and other applications." Since the mid-1990s the ASCII-based format has been treated as vendor-neutral (Wavefront OBJ / Alias/Wavefront OBJ / OBJ). It remains widely used, particularly for 3D printing of objects in multiple colors. The original specification uses an associated Wavefront Material Template Library (MTL) file to define colors and textures; the OBJ file invokes them by name. The format supports polygonal meshes or freeform curves and surfaces, with a simple physical structure of lines that start with keywords. The files most commonly encountered contain polygonal faces: v for vertex positions, f for faces (1-based indices), and optionally vn (vertex normals) and vt (texture / UV coordinates).

That is why a GLB-centered generator and an STL↔OBJ conversion step can coexist without being the same export: one is a runtime and DCC handoff with PBR already on the mesh; the other moves between a tessellation-only print format and a geometry format that can carry appearance through MTL.

The conversion step: local in the browser, one direction at a time

The STL to OBJ page is not a second generator. Its document title is STL to OBJ Converter. The meta description says: "Convert STL files to OBJ in your browser. Your file never leaves your device." The heading is STL → OBJ. The visible UI copy is "Choose a STL file to convert," "Processed locally in your browser," and a Convert button; the same "Processed locally in your browser" line appears again under the button. This note does not invent file-size limits, batch conversion, quality settings, or cloud processing — none of those are stated on the page. An "← All tools" control is visible; this note does not treat that control as a landing.

The other direction has the same local contract. The OBJ to STL page is titled OBJ to STL Converter. Its meta description is "Convert OBJ files to STL in your browser. Your file never leaves your device." The heading is OBJ → STL. The UI copy is "Choose a OBJ file to convert," "Processed locally in your browser," and Convert. Again, the page does not document batch jobs, size caps, or a server-side queue, and those are not added here.

A compact pipeline checklist

• Briefing, including the printable-parts use case and the drag-to-rotate gallery → the marketing homepage.
• Leave the generator with the documented handoff → GLB plus a rendered preview image, PBR included, into Blender, Unity, Unreal Engine, Three.js, Babylon.js, or model-viewer.
• Need a tessellation-only print or CAD interchange file, or the reverse → a separate in-browser conversion, one direction per page.
• STL in, a format that can carry appearance via MTL out → the STL-to-OBJ tool, processed locally; the file never leaves the device.
• OBJ in, an STL out → the OBJ-to-STL tool, same local contract.

Keep the generator's export FAQ and the converter meta descriptions in different slots. A printable-part use case on the homepage explains why STL and OBJ come up; it does not rewrite the generator's visible export list.