{"id":9114,"date":"2026-11-19T07:42:06","date_gmt":"2026-11-19T07:42:06","guid":{"rendered":"https:\/\/koitorhardware.com\/?p=9114"},"modified":"2026-11-19T07:42:06","modified_gmt":"2026-11-19T07:42:06","slug":"iges-vs-step","status":"publish","type":"post","link":"https:\/\/koitorhardware.com\/de\/iges-vs-step\/","title":{"rendered":"IGES vs STEP: Compare the Data That Actually Survives the Exchange"},"content":{"rendered":"<p>IGES vs STEP is a practical CAD exchange question, but neither file extension guarantees that every important design detail will survive a transfer. Many IGES exchanges carry curves and surfaces; STEP commonly carries solid models and can carry additional product information when the selected protocol and both software systems support it. IGES also has solid representation options. A buyer should choose the format the receiver can reliably import, then verify units, scale, geometry, assembly structure, revision and the manufacturing requirements sent with the model.<\/p>\n<h2>What the format names describe<\/h2>\n<p>IGES and STEP are neutral exchange approaches used to transfer product-design data between computer-aided design systems. They exist because a supplier, buyer or engineering partner may not use the same native software. Exporting a neutral file can make geometry available to another application without requiring the recipient to own the source system. It does not mean that the recipient receives the original editable feature history or every piece of engineering intent. An IGES vs STEP choice should reflect the receiver\u2019s validated import needs and the data the buyer expects to retain.<\/p>\n<p>IGES is an older exchange format and is often encountered in workflows involving curves, surfaces and wireframe or surface geometry. Some IGES implementations and options can represent solids, including manifold solid representations. It is therefore inaccurate to treat every IGES file as \u201csurface only.\u201d What a particular exporter writes and a particular importer reads depends on the software and settings used.<\/p>\n<p>STEP is a family of product-data exchange standards and protocols. A STEP file can represent solid geometry and, depending on the selected application protocol and implementation, may carry product structure or other product data. The <code>.step<\/code> oder <code>.stp<\/code> extension alone does not identify every capability in a specific file. An exported model may contain only geometry, while another transfer may include more information; the receiver\u2019s software and import settings matter.<\/p>\n<p>The buyer should think of the extension as a clue about the exchange route, not a guarantee of a valid model. A file can open while still having missing faces, incorrect units, fragmented surfaces, lost assembly relationships, an unexpected origin or a stale revision. The useful question is not only \u201cWhich format is better?\u201d but \u201cWhich required data does this recipient need, and how will both sides verify it?\u201d<\/p>\n<h2>Compare the data that may survive<\/h2>\n<div class=\"wp-block-table koitor-responsive-table\" style=\"max-width:100%;overflow-x:auto;\">\n<table style=\"width:100%;border-collapse:collapse;overflow-wrap:anywhere;\">\n<thead>\n<tr>\n<th>Handoff item<\/th>\n<th>IGES exchange<\/th>\n<th>STEP exchange<\/th>\n<th>What the recipient should verify<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Curves and surface geometry<\/td>\n<td>Common in practical IGES use<\/td>\n<td>Can also represent geometry<\/td>\n<td>Compare key profiles, surfaces and boundaries with the controlled drawing<\/td>\n<\/tr>\n<tr>\n<td>Solid representation<\/td>\n<td>Supported by some options and implementations; not universal for every export<\/td>\n<td>Commonly used for solid-model exchange<\/td>\n<td>Check whether the import produced the intended closed bodies<\/td>\n<\/tr>\n<tr>\n<td>Assembly structure<\/td>\n<td>May depend on export and recipient handling<\/td>\n<td>May be represented in supported protocols and workflows<\/td>\n<td>Confirm component count, hierarchy, orientation and part names as needed<\/td>\n<\/tr>\n<tr>\n<td>Native feature history<\/td>\n<td>Generally not the same as the source CAD feature tree<\/td>\n<td>Not guaranteed by neutral exchange<\/td>\n<td>Ask whether editable history is actually required or whether geometry is sufficient<\/td>\n<\/tr>\n<tr>\n<td>Product information<\/td>\n<td>Depends on implementation and transfer<\/td>\n<td>May carry additional data when protocol and software support it<\/td>\n<td>List which attributes, PMI or metadata must be retained and test the file<\/td>\n<\/tr>\n<tr>\n<td>Units and scale<\/td>\n<td>Must be confirmed during export\/import<\/td>\n<td>Must be confirmed during export\/import<\/td>\n<td>Check one known dimension against the drawing or reference<\/td>\n<\/tr>\n<tr>\n<td>Manufacturing requirements<\/td>\n<td>Not automatically established by model geometry<\/td>\n<td>Not automatically established by model geometry<\/td>\n<td>Send a controlled drawing, revision and written requirements separately<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The table is deliberately conditional. It is not a promise that all STEP files carry more information than all IGES files. Protocol, software version, import\/export options, model structure and validation determine what is present. If the buyer needs a particular type of product manufacturing information, assembly structure or metadata, name it explicitly and ask the sender and receiver to confirm a test transfer.<\/p>\n<figure class=\"wp-block-image size-large koitor-blog-image\" style=\"margin:32px 0;\"><img decoding=\"async\" src=\"https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step.webp\" alt=\"CAD handoff review comparing neutral IGES and STEP geometry against a controlled hardware drawing.\" style=\"width:100%;max-width:960px;height:auto;display:block;margin:0 auto;border-radius:10px;\"  srcset=\"https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step-18x10.webp 18w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step-150x150.webp 150w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step-300x169.webp 300w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step-768x432.webp 768w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step-1024x576.webp 1024w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-process-iges-vs-step.webp 1200w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" loading=\"lazy\"\/><figcaption style=\"font-size:14px;color:#667085;text-align:center;margin-top:8px;\">Check the imported model against the approved drawing and receiver\u2019s requirements.<\/figcaption><\/figure>\n<h2>The receiving check matters more than the extension<\/h2>\n<h3>Confirm units and scale<\/h3>\n<p>A model that looks correct on screen may be imported at the wrong scale. Before using a received file for quotation, tooling or manufacturing, compare one or more known dimensions against the controlled drawing. Check the units shown by the source, the import units selected by the recipient and any conversion performed by the software. Do not rely on visual proportions alone, especially when the part is small, symmetrical or displayed without a measurement reference.<\/p>\n<p>If the file contains an assembly, verify that representative component dimensions remain plausible and that parts retain their relative locations. A single overall bounding-box dimension may not identify every scale or orientation problem. If the geometry is unfamiliar, request a dimensioned drawing or a marked-up screenshot with the critical dimensions rather than assuming that a successful import dialog means the model is ready.<\/p>\n<h3>Check surfaces, bodies and gaps<\/h3>\n<p>After import, determine what the application created: a closed solid body, multiple solids, a set of surfaces, curves, or a mixture. This distinction affects what downstream operations are available. A surface model may be useful for reference or complex shape exchange but may require additional work before a solid-based manufacturing or mass-property operation. A model can appear visually complete while containing an open boundary or a small gap that changes how the recipient\u2019s software treats it.<\/p>\n<p>Use the receiver\u2019s normal model-checking tools and compare the result to the drawing. Ask the recipient to report obvious missing faces, duplicate geometry, unexpected fragments or repair operations that alter the shape. If the file requires healing or stitching, record what was done and ask for approval when the repair could change a controlled feature. Do not assume automatic repair has preserved every dimension simply because the software displays a model.<\/p>\n<h3>Verify orientation, coordinate system and assembly organization<\/h3>\n<p>A single part may import at an unexpected origin or orientation. That may be harmless for a standalone component if the drawing defines datums, but it can cause confusion in a multi-part assembly. Confirm that the model is oriented as intended and that mating parts remain in the right relative position. If the recipient needs part names, hierarchy or component identifiers for quoting or planning, confirm whether those attributes survived and whether they match the bill of materials.<\/p>\n<p>An assembly can also be flattened into geometry or split into individual bodies depending on export settings and the receiving system. Ask whether the supplier needs an assembly file, individual part files or both. Keep the part number and revision attached to each component where possible. Do not treat a collection of visible solids as a complete assembly definition if fasteners, purchased components, constraints or BOM data are required separately.<\/p>\n<h3>Confirm what \u201ceditable\u201d means<\/h3>\n<p>A neutral file generally should not be promised to retain the original authoring history in the same way as a native file. A recipient may be able to edit imported geometry, add features or use direct-modeling tools, but that is different from recovering the source sketch, parametric constraints, design tree or intent. If the recipient needs to change dimensions, say which edits are expected and ask whether a native file is required, whether the neutral geometry is sufficient, or whether a drawing and change request are more appropriate.<\/p>\n<p>This distinction prevents a common expectation mismatch. A buyer may say \u201ceditable CAD\u201d while meaning only that the supplier can measure the model or create a fixture. A product engineer may mean that the original feature tree must remain fully parametric. Those are different deliverables. Define the intended downstream work before choosing a format or asking the exporter to provide multiple files.<\/p>\n<h2>Use the file with a controlled drawing and RFQ<\/h2>\n<p>A three-dimensional model communicates shape, but it may not define every manufacturing requirement. A model may omit tolerances, material, finish, weld locations, cosmetic faces, inspection criteria, packaging or approved substitutions. Those items should be stated in a controlled drawing, specification or RFQ attachment. A neutral format does not make an unspecified design requirement appear automatically.<\/p>\n<p>For metal hardware, the recipient may need a 3D model for overall shape and component relationships, while the drawing controls critical dimensions and product acceptance. The buyer should identify which document governs if a model and drawing conflict. Add revision identifiers to both the model and drawing, and state whether the file is for reference, quotation, prototype or production. A filename alone can be renamed, so preserve the revision in the document metadata or a controlled accompanying record when practical.<\/p>\n<p>A sensible handoff package may include the neutral model, a dimensioned drawing, a BOM or component list when needed, material and finish requirements, and a short note describing the intended operations. This guide does not duplicate a complete RFQ file checklist; it focuses on geometry exchange. If the buyer\u2019s broader question is which attachments to include, the existing RFQ guide owns that broader file-set topic.<\/p>\n<p>The handoff note should describe the source of truth, not just list file names. Identify the part number, drawing revision, model revision, intended use and any known limitations. If a model is a preliminary envelope or concept, mark it as not approved for production. If the drawing controls dimensions while the model controls overall shape, state that division. If the model and drawing are expected to match exactly, say so and ask the recipient to report a discrepancy before quoting or making a sample.<\/p>\n<p>File naming helps, but naming alone is not revision control. A filename can be changed during email forwarding or upload. Include a revision field in the drawing or a controlled exchange note, and retain the files together in the project record. When replacing a file, identify what changed and whether the earlier version should be removed from the recipient\u2019s working folder. Ask the supplier to confirm that it has replaced the previous model rather than leaving two similarly named files in an active job directory.<\/p>\n<p>For assemblies, the handoff may need a component list that connects model instances to part numbers and quantities. A STEP import that displays several solid bodies does not necessarily preserve the product hierarchy expected by purchasing or assembly planning. If a supplier needs individual manufacturing files, state whether each component should be exported separately or whether the assembly context is needed for fit review. The supplier should not infer purchased screws, anchors or inserts from a rendering if those parts are absent from the model or BOM.<\/p>\n<p>Consider a small transfer test when a project involves a new supplier, software combination or complicated assembly. Send one representative part or subassembly, ask the actual receiver to import it, and review known dimensions and structure together. This is a compatibility check for that workflow, not a general certification that every future file will import correctly. Record the version or protocol used when it affects the exchange and repeat the check after a substantial software or export-setting change.<\/p>\n<p>When a receiver asks for both IGES and STEP, clarify why. It may be testing compatibility, preserving an alternate representation or supporting different software. More files do not automatically create more certainty. Each copy should identify the same part and revision, and any differences should be explained rather than left for the supplier to reconcile.<\/p>\n<h2>A practical export and import workflow<\/h2>\n<ol>\n<li><strong>Agree on the intended use.<\/strong> Identify whether the file is for quotation, design review, sampling, tooling or production.<\/li>\n<li><strong>Ask what the recipient can import.<\/strong> Confirm the software and preferred format or protocol with the actual receiver.<\/li>\n<li><strong>Choose the necessary content.<\/strong> State whether the recipient needs geometry only, an assembly, attributes or other product data.<\/li>\n<li><strong>Export from the controlled source.<\/strong> Record the source model revision and relevant export settings where needed.<\/li>\n<li><strong>Send the drawing and written requirements.<\/strong> Include dimensions, material, finish, critical features and the document that controls.<\/li>\n<li><strong>Import and inspect.<\/strong> Check units, scale, body\/surface result, missing geometry, assembly structure and orientation.<\/li>\n<li><strong>Compare critical dimensions.<\/strong> Use the approved drawing or known dimensions, not screen appearance alone.<\/li>\n<li><strong>Resolve repairs or gaps.<\/strong> Have the responsible design owner approve changes that may alter controlled geometry.<\/li>\n<li><strong>Confirm receipt and revision.<\/strong> Ask the recipient to identify the file and revision it will use.<\/li>\n<\/ol>\n<p>This process is intentionally simple. A small prototype may need only a clean model and drawing check; a complex assembly or controlled product data exchange may require a formal validation plan. Match the rigor to the risk and downstream use. Do not promise universal interoperability based only on a format extension or vendor statement.<\/p>\n<h3>Decide which format to request<\/h3>\n<p>Ask the recipient which format it prefers before exporting. If it can reliably import a STEP file with the required solid or assembly structure, STEP may be the practical choice for that workflow. If the receiver\u2019s system or legacy process uses IGES for a particular surface model, that may be the more useful exchange. These are workflow-specific decisions, not a claim that one format always contains more usable information. The recipient\u2019s actual software behavior and the project\u2019s data requirements should decide.<\/p>\n<p>When you are not sure what the receiver needs, send a short question rather than attaching every possible extension. Ask whether it needs a solid, a surface model, a component assembly, individual part files, metadata, or simply a visual reference for quotation. Ask whether a dimensioned drawing must accompany the model. A clear answer reduces the risk of a supplier pricing an incomplete concept or treating a reference model as approved production data.<\/p>\n<p>The buyer can keep a reusable exchange checklist in the project handoff: format and protocol requested, source revision, units, intended use, required body or assembly structure, critical dimensions to verify, drawing\/specification links and a contact for technical questions. The checklist is not a new standard or a certification. It records the assumptions agreed for that project so that a later update can be compared with the prior transfer.<\/p>\n<p>If an imported model fails one of the checks, decide whether the issue is a transfer problem, a source-model issue or an incomplete manufacturing requirement. A receiver might repair a small geometry defect, but a product owner should approve a change to a critical hole, mating face or envelope. If the model lacks a tolerance, request drawing clarification rather than asking the CAD recipient to infer a value from the imported geometry. Keeping these decisions distinct makes the exchange traceable and prevents format troubleshooting from becoming an undocumented design change.<\/p>\n<h2>Hypothetical hardware example<\/h2>\n<p>Imagine a buyer sending a mounting bracket assembly to a supplier for a quotation. The model opens successfully, but the recipient reports that the assembly imported as several surfaces and one solid body. The overall silhouette looks right. Before quoting, the buyer and supplier should compare the part count, units, one known dimension, hole positions and the drawing revision. They should also clarify whether the surfaces are sufficient for the quote or whether the supplier needs a clean solid representation.<\/p>\n<p>If the recipient repairs a gap or stitches surfaces, the buyer should ask whether any critical dimensions changed. If the issue is only format compatibility, the designer can export another representation and repeat the same receiving checks. If the drawing omits a tolerance or finish, switching formats will not resolve that missing requirement; the design owner should clarify it separately. The accepted exchange record should say which file and revision the supplier used.<\/p>\n<p>This example is hypothetical. It is not a Koitor customer project, a software test result, a format guarantee or a claim that Koitor accepts every CAD protocol. It demonstrates the received-file questions that make an exchange useful for sourcing.<\/p>\n<figure class=\"wp-block-image size-large koitor-blog-image\" style=\"margin:32px 0;\"><img decoding=\"async\" src=\"https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step.webp\" alt=\"Buyer checklist for IGES vs STEP file handoff covering units, geometry, assembly, revision and drawing requirements.\" style=\"width:100%;max-width:960px;height:auto;display:block;margin:0 auto;border-radius:10px;\"  srcset=\"https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step-18x10.webp 18w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step-150x150.webp 150w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step-300x169.webp 300w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step-768x432.webp 768w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step-1024x576.webp 1024w, https:\/\/koitorhardware.com\/wp-content\/uploads\/2026\/11\/k1767-checklist-iges-vs-step.webp 1200w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" loading=\"lazy\"\/><figcaption style=\"font-size:14px;color:#667085;text-align:center;margin-top:8px;\">Confirm the imported data and document revision before using the model.<\/figcaption><\/figure>\n<h2>Common CAD handoff mistakes<\/h2>\n<ul>\n<li><strong>Assuming every IGES file contains only surfaces.<\/strong> Some options and implementations support solid representations; inspect the actual file.<\/li>\n<li><strong>Assuming every STEP file is a complete solid assembly.<\/strong> Content depends on protocol, export settings and receiver support.<\/li>\n<li><strong>Treating a successful import as proof of correctness.<\/strong> Check scale, units, geometry and revision.<\/li>\n<li><strong>Expecting native feature history to survive.<\/strong> Define whether editable geometry or native parametric history is required.<\/li>\n<li><strong>Sending a model without a drawing.<\/strong> Geometry may not state tolerance, finish, material or inspection requirements.<\/li>\n<li><strong>Comparing screen images instead of dimensions.<\/strong> Verify known dimensions and critical features.<\/li>\n<li><strong>Ignoring assembly structure.<\/strong> Confirm component count, hierarchy, orientation and identifiers where needed.<\/li>\n<li><strong>Letting a repair go undocumented.<\/strong> Review any geometry repair that may alter controlled features.<\/li>\n<li><strong>Sending several formats without a source of truth.<\/strong> Identify the governing file and revision.<\/li>\n<li><strong>Assuming all recipient software behaves alike.<\/strong> Test the actual receiver\u2019s workflow instead of relying on a general compatibility claim.<\/li>\n<\/ul>\n<h2>H\u00e4ufig gestellte Fragen<\/h2>\n<h3>Which is better, IGES or STEP?<\/h3>\n<p>Neither is universally better. Choose the format and data content that the actual receiver can import and verify for the intended use. STEP is commonly used for solid exchange and may support additional product data; IGES is still encountered for curves and surfaces and can support solid representations in some implementations.<\/p>\n<h3>Does IGES only contain surfaces?<\/h3>\n<p>No. Practical IGES exchanges often use curves and surfaces, but some implementations support solid representation options. Check the content of the file and the recipient\u2019s importer rather than relying on an absolute rule.<\/p>\n<h3>Does STEP always preserve the whole assembly?<\/h3>\n<p>No. Assembly organization and additional product data depend on the selected protocol, export settings and software support. Verify component count, hierarchy and required attributes after import.<\/p>\n<h3>Will either format preserve the native CAD feature tree?<\/h3>\n<p>Do not assume so. A neutral exchange may provide geometry without the original parametric history. Ask for a native file only when the downstream task requires it and the sender is authorized to provide it.<\/p>\n<h3>What should I check after importing a CAD file?<\/h3>\n<p>Confirm units, scale, dimensions, body or surface structure, missing faces, assembly orientation, revision and any required product data. Compare critical features with the controlled drawing.<\/p>\n<h3>Is a 3D model enough for a manufacturing quote?<\/h3>\n<p>Not always. Material, tolerances, finish, critical features, inspection, packaging and other acceptance requirements may need a drawing or written specification.<\/p>\n<h3>Should I send both IGES and STEP?<\/h3>\n<p>Only when the receiver requests or needs both. Identify the authoritative revision and explain any differences. Duplicated files without clear control can create confusion.<\/p>\n<h3>How can Koitor support a CAD handoff?<\/h3>\n<p>Koitor Hardware is a family-owned custom metal hardware factory with approved drawing and sample communication. Share the model together with a controlled drawing and project requirements so the receiver can confirm the format it can use. This does not guarantee support for every protocol or software version.<\/p>\n<h3>Sources and scope<\/h3>\n<ul>\n<li><a href=\"https:\/\/transmagic.com\/iges-vs-step\/\" rel=\"nofollow noopener\" target=\"_blank\">TransMagic: IGES vs STEP<\/a><\/li>\n<\/ul>\n<p><strong>Scope note:<\/strong> Format capabilities depend on the actual exporter, importer, protocol and settings. This article does not promise universal compatibility or reconstruct a current protocol specification. Confirm the exact received data with the intended software recipient.<\/p>\n<section class=\"koitor-blog-cta\" style=\"margin:36px 0 0;padding:28px;border:1px solid #E5E7EB;border-radius:12px;background:#ffffff;\">\n<h3 style=\"margin:0 0 12px;color:#172B4D;\">Review a CAD handoff for a custom hardware project<\/h3>\n<p>Share the model, controlled drawing, revision and intended manufacturing use. Koitor can discuss the surrounding custom metal hardware project within its confirmed scope.<\/p>\n<div style=\"display:flex;gap:12px;flex-wrap:wrap;align-items:center;margin-bottom:24px;\">\n    <a href=\"https:\/\/koitorhardware.com\/de\/kontakt\/\" style=\"display:inline-flex;align-items:center;justify-content:center;min-height:48px;padding:0 22px;border-radius:8px;background:#FF5A1F;color:#ffffff;font-weight:700;text-decoration:none;line-height:1;\">Angebot anfordern<\/a><br \/>\n    <a href=\"https:\/\/koitorhardware.com\/de\/oem-home-storage-hardware-manufacturer\/\" style=\"display:inline-flex;align-items:center;justify-content:center;min-height:48px;padding:0 22px;border-radius:8px;border:1px solid #FF5A1F;color:#FF5A1F;background:#ffffff;font-weight:700;text-decoration:none;line-height:1;\">OEM Hardware Projects<\/a>\n  <\/div>\n<div class=\"koitor-article-tags\" style=\"margin-top:24px;padding-top:18px;border-top:1px solid #E5E7EB;display:flex;align-items:center;gap:8px;flex-wrap:wrap;\">\n    <span style=\"font-size:14px;font-weight:700;color:#344054;margin-right:4px;\">Stichw\u00f6rter:<\/span><br \/>\n    <span style=\"display:inline-flex;align-items:center;justify-content:center;padding:6px 12px;border-radius:999px;background:#FFF3ED;color:#FF5A1F;font-size:13px;font-weight:600;line-height:1.2;\">Kaufratgeber<\/span><br \/>\n    <span style=\"display:inline-flex;align-items:center;justify-content:center;padding:6px 12px;border-radius:999px;background:#FFF3ED;color:#FF5A1F;font-size:13px;font-weight:600;line-height:1.2;\">OEM &amp; Produktentwicklung<\/span><br \/>\n    <span style=\"display:inline-flex;align-items:center;justify-content:center;padding:6px 12px;border-radius:999px;background:#FFF3ED;color:#FF5A1F;font-size:13px;font-weight:600;line-height:1.2;\">Metal Hardware<\/span>\n  <\/div>\n<\/section>","protected":false},"excerpt":{"rendered":"<p>Compare IGES and STEP as neutral CAD exchange formats, then verify what the recipient actually imported.<\/p>","protected":false},"author":1,"featured_media":9111,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[145],"tags":[415,139,425],"class_list":["post-9114","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hardware-sourcing-knowledge","tag-buyer-guides","tag-metal-hardware","tag-oem-product-development-2"],"_links":{"self":[{"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/posts\/9114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/comments?post=9114"}],"version-history":[{"count":1,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/posts\/9114\/revisions"}],"predecessor-version":[{"id":9161,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/posts\/9114\/revisions\/9161"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/media\/9111"}],"wp:attachment":[{"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/media?parent=9114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/categories?post=9114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/koitorhardware.com\/de\/wp-json\/wp\/v2\/tags?post=9114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}