Assimp Import

On this page

Import mesh assets from different tools

Product teams receive models from designers, visualization tools, and digital libraries. Assimp Import gives your application a common way to read supported mesh assets and bring them into an engineering workflow.

Use it to expand a viewer, prepare content for a product portal, or combine polygonal assets with CAD data.

How it works

Select an input file and read its mesh objects, placements, and available materials. Your application can show those objects in a scene, let users select them, and pass their geometry to other tools. Add a separate writer when users need an output file.

Keep objects and materials organized

Import mesh geometry together with available colors, materials, and scene structure. Users can inspect an asset, identify its objects, and work with its appearance as part of your application.

Cover a wider set of inputs

Supported input routes include .blend, .3ds, .3mf, .ac, .amf, .ase, .dae, .x3d, and PLY. File formats carry different information, so choose sample assets with the structure and materials your users need.

Browse conversion guides to connect an input reader with a suitable output writer.

Use one import process for several asset sources

Use the same selection and processing tools for assets from different design programs. Imported assets remain polygonal geometry; creating editable CAD surfaces requires a separate reconstruction process.

Prepare large assets for review

Similar-looking files can contain very different amounts of data. Object count, mesh detail, scene organization, and material resources all affect loading and display. Consistent import settings help teams prepare these assets for their viewing or processing task.

Units, orientation, object positions, and surface normals determine whether a model appears as intended. Materials may also depend on external resources. Making missing information clear helps users decide whether an asset is ready for use.

Give content teams one place to review incoming assets

A product portal may receive models from an industrial designer, a supplier, and a visualization agency. Each sends a different supported mesh format. Maintaining a separate review tool for every source makes it harder to answer basic questions about scale, missing materials, and object placement.

Assimp Import can provide a shared reading stage inside your content application. Reviewers can inspect imported objects, confirm their orientation and appearance, and identify assets that need correction before publication. Your application can keep the original file and record which checks were completed.

This helps a content manager organize acceptance around the result users will see. Missing texture resources can go back to the asset provider, while accepted models move to browser preparation or a separate export step. Teams can add supported asset sources without redesigning the whole review experience.

Prepare assets for their next use

Send imported meshes to Light Web Viewer for browser review or add a separate writer for conversion. Mesh-capable STEP, STEP XML, and DXF routes can carry polygonal geometry into CAD document workflows.

For a closed envelope around imperfect tessellation, see Surface Wrapping. For CAD surfaces fitted to measured points, see Surface from Scattered Points.

Show us the assets you receive and where they need to go. We can help select an import and preparation path.