Free online STEP to PLY converter

Mesh-processing software, scanner pipelines, and some visualization tools accept PLY meshes but cannot use STEP's CAD solid geometry directly. Converting produces a polygon mesh for display, analysis, or further mesh editing; it does not retain an editable CAD model.

STEP and PLY formats

STEP, stored as .step or .stp, is the ISO 10303 product-data exchange format used by mechanical CAD systems including SolidWorks, CATIA, Siemens NX, PTC Creo, Autodesk Inventor, Fusion, Onshape, and FreeCAD. A STEP file normally stores boundary-representation geometry: mathematically defined solids, surfaces, curves, and assemblies rather than triangles.

STEP application protocols such as AP203, AP214, and AP242 can carry differing amounts of product structure, names, colors, and product-manufacturing information. The geometry is precise within its modeling tolerance, but CAD features such as sketches, parametric history, and native constraints are generally not transferred.

PLY, also called Polygon File Format or Stanford Triangle Format, stores mesh vertices and faces. It can store normals and per-vertex or per-face properties such as RGB/RGBA color; the supported properties depend on both the exporter and receiving application. PLY is common in 3D scanning, point-cloud processing, MeshLab, CloudCompare, research workflows, and mesh visualization.

PLY may be ASCII or binary. Binary PLY is usually smaller and faster to read, while ASCII PLY is easier to inspect in a text editor. PLY has no standard unit field, no CAD assembly hierarchy, and no standard representation for exact cylinders, planes, or surfaces.

Convert the file

Upload the .step or .stp file to the converter on 101convert.com, choose PLY as the output format, convert it, and download the mesh. Open the result in the intended application and check a known dimension, curved areas, and separate components before relying on it.

For local conversion and control over tessellation, use FreeCAD:

1. Open the STEP file with File → Open or File → Import.
2. In the model tree, select the solid, compound, or required individual parts.
3. Switch to the Mesh Design workbench.
4. Choose Meshes → Create mesh from shape.
5. Set the linear and angular tessellation tolerances in the mesh dialog, then create the mesh.
6. Select the new mesh object and choose File → Export.
7. Select the PLY mesh format and save, for example, as part.ply.

MeshLab is useful for inspecting, cleaning, decimating, and re-exporting the resulting PLY, but it does not normally import STEP directly. Export the STEP model to a mesh first, then open that mesh in MeshLab using File → Import Mesh.

Mesh quality and compatibility

The conversion is a tessellation: analytic surfaces become finite polygons, usually triangles. A smaller linear deflection and tighter angular tolerance approximate curves more closely, but create more faces, larger files, and higher memory use. Use a tolerance based on the smallest feature and accuracy required by the destination workflow.

Inspect holes, fillets, thin walls, narrow gaps, and curved edges after export. Coarse tessellation can make round holes visibly polygonal, merge nearby surfaces, omit small features, or leave unsuitable geometry for downstream processing. Extremely fine tessellation can create millions of triangles with little visible benefit.

For 3D printing, PLY is not the usual delivery format; STL and 3MF are more widely accepted by slicers. Use PLY only when the receiving software specifically requires it, and verify that the exported mesh is closed and manifold if the downstream process requires a watertight solid.

STEP assemblies can contain multiple named parts, while a PLY export commonly becomes one mesh without assembly relationships. Export components separately when the receiving application needs independently selectable parts.

STEP colors do not automatically become PLY colors. If color is required, verify that the exported file contains color properties and that the target program reads the same vertex- or face-color convention. Because PLY coordinates are unitless, measure a known feature after import; scale only if the target program interprets the coordinates using a different unit system.