Vocabulary for 3D Printing and Additive Manufacturing

Software engineers who build tooling for 3D printers, CAD pipelines, or manufacturing automation need a working vocabulary that spans mechanical processes and software concepts. Whether you’re writing a slicer, a print-queue manager, or a monitoring dashboard for a print farm, this vocabulary lets you discuss failures and design decisions precisely with both hardware and software colleagues.

Key Vocabulary

Slicing The process of converting a 3D model into a sequence of thin, printable layers, along with the toolpath instructions (G-code) that tell the printer how to build each layer. Example: “The slicer is generating unnecessary travel moves between islands on this layer — we should enable combing to reduce stringing.”

G-code The low-level machine instruction format that tells a 3D printer exactly how to move its axes, at what speed, and when to extrude material. Example: “The custom G-code we inject before each print homes the axes and runs a bed-leveling probe sequence.”

Infill The internal structure printed inside a solid model, typically a repeating pattern (like a grid or gyroid) at a percentage density, balancing strength against material use and print time. Example: “We’re defaulting to 20% gyroid infill for these parts — it gives good strength in all directions without excessive print time.”

Layer adhesion The strength of the bond between successive printed layers, which determines the part’s structural integrity, especially along the Z-axis. Example: “Poor layer adhesion on this print is likely a temperature issue — the nozzle may be cooling too much between layers.”

Warping Distortion of a printed part, usually at the corners or edges, caused by uneven cooling and shrinkage of the material during printing. Example: “We’re seeing warping on large flat parts; increasing the bed temperature and adding a brim should help.”

Support structures Temporary, printed scaffolding that holds up overhanging or unsupported sections of a model during printing, removed after the print completes. Example: “The overhang on this bracket exceeds 45 degrees, so the slicer is automatically generating support structures underneath it.”

Bed leveling / calibration The process of ensuring the print surface is parallel to the printer’s movement plane at a consistent nozzle distance, critical for first-layer adhesion. Example: “We added an automatic bed-leveling routine using a probe, so operators no longer have to calibrate manually before each print.”

Print farm A collection of multiple 3D printers, often managed centrally through software, used to run many print jobs in parallel at scale. Example: “The print farm dashboard shows which of the 40 printers are idle, printing, or flagged for a failed job.”

Toolpath The specific path a printer’s nozzle (or laser, in other additive processes) follows to deposit or fuse material for a given layer. Example: “The generated toolpath for this layer has a lot of unnecessary retractions, which is adding several minutes to the print time.”

Common Phrases

In code reviews:

• “This slicer setting change affects retraction distance globally — can we scope it per-material profile instead of hardcoding it?”
• “We’re not validating that the G-code stays within the printer’s build volume before sending it to the machine.”
• “The infill pattern generator is producing self-intersecting geometry on non-manifold meshes — we should reject those at import time.”

In standups:

• “Yesterday I fixed a bug where the slicer miscalculated support density on steep overhangs; today I’m adding a print-time estimator.”
• “I’m investigating a spike in failed prints on printer 12 — the logs show repeated thermal runaway shutdowns.”
• “I finished the queue manager’s retry logic; if a print fails a filament-run-out check, it now pauses instead of continuing blind.”

In cross-functional meetings with hardware/process engineers:

• “Can we get the recommended nozzle temperature range for this new filament so we can update the material profile in software?”
• “We’re seeing a correlation between ambient humidity and layer adhesion failures — is that consistent with what you’re seeing on the shop floor?”
• “The camera-based failure detection is flagging false positives on normal stringing — we need better labeled training data.”

Phrases to Avoid

Saying “the print broke” for any failure. This is too vague for diagnosis. Native speakers distinguish between “the print failed” (didn’t complete), “the part warped,” “there was a layer shift,” and “the nozzle clogged” — each pointing to a completely different root cause.

Saying “the printer stopped” instead of naming the specific fault. Say instead: “the printer paused for a filament-run-out,” “it triggered a thermal safety shutdown,” or “it lost steps and the print head crashed into the part.” Vague descriptions send hardware engineers troubleshooting the wrong subsystem.

Saying “make it stronger” instead of specifying the mechanical property. In engineering English, “strong” is imprecise. Specify whether you mean tensile strength, layer adhesion, impact resistance, or resistance to warping — each is addressed by different print settings.

Quick Reference

Term	How to use it
slicing	”The slicer generates G-code from the 3D model layer by layer.”
infill	”20% gyroid infill balances strength and print time well here.”
layer adhesion	”Poor layer adhesion here suggests the nozzle temperature is too low.”
warping	”Warping on large flat parts often means the bed temperature is too low.”
support structures	”Overhangs past 45 degrees need generated support structures.”
print farm	”The print farm dashboard flags printer 12 for repeated failures.”

Key Takeaways

• Be specific about failure types (warping, layer shift, clogging, thermal shutdown) rather than saying a print “broke” or “stopped.”
• Distinguish mechanical properties precisely (tensile strength vs. layer adhesion vs. warp resistance) when discussing quality issues.
• Slicing vocabulary (G-code, toolpath, infill, support structures) is the shared language between software tooling and the physical printing process.
• When collaborating with process or hardware engineers, connect software behavior explicitly to physical outcomes they can observe on the shop floor.
• Print farm and monitoring vocabulary (queue, retry, failure detection) mirrors distributed systems language — use it to bridge the two domains in conversation.

In Practice: Navigating Nuance – A Developer’s Perspective

Let’s be honest; translating technical concepts across languages isn’t always a simple one-to-one mapping. Even within the English language itself, subtle differences in phrasing can significantly impact understanding and collaboration, particularly when discussing complex topics like 3D printing. For developers new to additive manufacturing terminology, it’s not just about knowing what something is; it’s about conveying that knowledge precisely and effectively. This is where a deep appreciation for nuance becomes critical.

Consider a code review comment on a slicer implementation. A native English speaker might simply state: “This infill pattern isn’t optimal for strength.” But a non-native speaker, perhaps accustomed to more direct phrasing, could be misinterpreted. The ambiguity of “optimal” leaves room for debate – what constitutes ‘optimal’? A better approach would be: “This rectilinear infill pattern exhibits low tensile strength compared to gyroid. Consider exploring denser patterns or adjusting the infill percentage to improve structural integrity.” Notice how explicitly stating why it’s suboptimal and suggesting a concrete alternative immediately clarifies the issue. Similarly, in a Slack message describing a pull request for a new feature, saying “I’ve added support for adaptive layer height” is less effective than “I’ve implemented adaptive layer height, dynamically adjusting layer thickness based on geometry complexity to minimize material usage and improve surface finish.”

The key difference lies in the level of detail and justification. When discussing print failures, avoid vague terms like “the print failed.” Instead, describe the specific issue: “Layer adhesion was compromised due to insufficient bed temperature, resulting in warping.” This allows for targeted troubleshooting – adjusting the bed temperature directly addresses the root cause. Furthermore, be mindful of passive voice; active voice is generally preferred in professional communication as it clarifies who or what performed an action.

It’s also important to understand the context within which these terms are used. “Print resolution” isn’t just about pixel count; it’s tied directly to layer height and nozzle diameter, impacting both surface finish and build time. Being able to articulate this connection is a sign of deeper understanding and demonstrates an ability to translate abstract concepts into actionable solutions – something that’s incredibly valuable in any development environment.

# Example: Using Cura's command line interface (CLI) for adjusting infill density
cura --profile "MyProfile" --command "set_infill_density 75"

This CLI example, using cura and its command-line interface, showcases a practical application of understanding infill parameters. The command directly sets the infill density to 75%, illustrating how developers might interact with slicing software programmatically – a skill that’s increasingly relevant as additive manufacturing becomes more integrated into automated workflows. The ability to interpret and execute such commands demonstrates not just vocabulary knowledge, but also an understanding of the underlying processes involved in 3D printing.