This article proposes a production-ready parametric workflow for custom footwear that converts three inputs, a 3D foot scan, an activity profile, and a style preset, into printable uppers and graded midsole geometries with traceable outputs. It sets out a practical implementation in either Grasshopper (Rhino 8) or Houdini 20, including registration to a canonical frame, last generation, rocker control, lattice family selection, and region-based density grading driven by measured or synthesised pressure fields. The approach is designed to be auditable: it includes geometry validation (manifold, thickness, strut limits), versioned parameter manifests, and a defined export suite for print and review. The rationale leans on evidence that region-tuned cellular midsoles can reduce plantar pressure when stiffness is controlled by zone, supporting graded structures rather than uniform lattices [1]. It also leverages Rhino 8’s tooling for creating watertight, print-checkable meshes as a dependable step in a fast iteration loop [2]. For stakeholder sign-off, it pairs lightweight web previews with Apple-native USDZ review so non-technical reviewers can confirm scale and intent without installing a dedicated app [6].
[1] P. Baranowski et al., “Influence of 3D-printed cellular shoe soles on plantar pressure and footwear performance,” Engineering Analysis with Boundary Elements, 2024. Available: ScienceDirect. ScienceDirect
[2] McNeel, “New in Rhino 8,” product documentation, 2024. Available: Rhino3D website. www.rhino3d.com
[3] SideFX, “What’s new in Houdini 20,” product documentation, 2023–2024. Available: SideFX documentation. SideFX
[4] Khronos Group, “KTX 2.0, GPU texture container format,” standards page, 2021–2024. Available: Khronos website. The Khronos Group
[5] Khronos Group, “Universal GPU compressed textures for glTF using KTX 2.0,” technical overview, 2021. Available: Khronos website. The Khronos Group
[6] Apple, “Quick Look Gallery,” developer documentation, 2024. Available: Apple Developer. Apple Developer
[7] TPM3D, “3D printed footwear solution reduces production time,” press release, Jul. 8, 2025. Available: TPM3D English site. TPM3D
[8] K. Chhikara et al., “Does scanner choice matter for the design of foot orthosis?,” Applied Bionics and Biomechanics, 2025. Available: PubMed Central. PMC
[9] SideFX, “What’s new in H20,” product page, accessed Nov. 20, 2025. Available: SideFX website. SideFX
Custom footwear has moved from experimental showcase to repeatable workflow. With reliable foot scanning on consumer devices, stable TPU print profiles, and lightweight web viewers for stakeholder sign-off, a parametric tool that converts three inputs, a foot scan, an activity profile, and a style preset, into printable uppers and midsoles is now achievable with mainstream software. This article sets out a production-ready approach in Grasshopper or Houdini, with validated geometry rules, export standards, and references for teams that want traceable, testable outcomes rather than one-off prototypes.
Additive manufacturing in footwear has progressed from partial midsoles to full printed constructions that ship at scale, supported by improvements in lattice design, materials, and downstream finishing. Recent academic work reports pressure reduction and comfort gains from cellular midsoles when geometry is tuned by region, which supports the case for graded structures driven by real or synthesised plantar data [1]. At the same time, platform updates in Rhino 8 simplify watertight mesh generation for print, while Houdini 20 improves procedural control and USD workflows for large lattice scenes [2], [3]. On the distribution side, glTF with Draco and KTX2 compresses assets for web preview, and USDZ remains the simplest route for native previews on Apple devices [4], [5], [6]. These capabilities combine to enable a compact tool that accepts minimal inputs, produces print-checked STLs, and shares lightweight 3D previews for review.
The system takes three inputs, a 3D foot scan, an activity profile, and a style preset.
For SLS TPU, treat as the primary route for wearable prototypes and pilots. Typical settings, layer height 0.12 to 0.20 millimetres, minimum wall 1.2 to 1.6 millimetres, practical strut diameters 0.8 to 1.2 millimetres, and shrinkage compensation between 0.3 and 0.6 percent, subject to material data sheets and vendor calibration. For MJF PA12 or other rigid nylons, use for structural prototypes where flexibility is less important; minimum walls tend to be higher, around 1.5 millimetres. FDM is useful for quick form checks, but wall and strut limits reduce fidelity for lattices. Resin systems can deliver clean surfaces for uppers and fixtures, however enclosed lattices require drain holes at regular spacing for post-processing. Industry releases in 2024 and 2025 have shown reduced print times and TPU recipes aimed at footwear, which confirms a wider range of viable production setups, although project teams should validate locally before committing to batch sizes [7].
Device choice, scan posture, and weight bearing affect geometry. Recent studies on orthosis design indicate that design changes are more sensitive to weight-bearing state than to the specific scanner model, which implies the workflow should enforce consistent capture conditions rather than over-optimising for device brand [8]. For consumer capture, require a consistent stance and short guided sweep; apply ICP to align to the canonical last; and decimate for responsive interaction. Target dimensional error under ±0.5 millimetres at critical regions such as the instep and toe box. Maintain toe clearance in the range of 3 to 5 millimetres to account for motion and socks. These numbers are practical rather than normative; the team should record local validation results alongside each print file.
Stakeholders need to confirm size and style before print. Publish a GLB with Draco geometry compression and KTX2 textures for quick loading in a Three.js viewer. Add clip planes to inspect the lattice, an on-model scale overlay with key dimensions, and a parameter manifest that captures the exact inputs and preset versions used for the build. For iOS and visionOS review, link a USDZ file to Quick Look so that teams can view the object at scale in situ without installing an app [5], [6]. This combination reduces misunderstandings and shortens review cycles; it also becomes a lightweight archive of what was printed and why.
Both routes are viable.
Grasshopper in Rhino 8 suits teams that already model footwear lasts and uppers in Rhino. Use Kangaroo components for relaxation, Dendro or OpenVDB for voxel operations, and custom C# or Python nodes for grading logic and manifold repair. Rhino 8 brings ShrinkWrap for watertight meshes and performance improvements that benefit interactive previews [2]. Distribute a single Grasshopper file with embedded clusters for scan alignment, last build, lattice selection, and export.
Houdini 20 suits teams that want scale and deeper control. Use VDB nodes for shelling and booleans, Attribute Wrangles for grading fields, and Labs tools for retopology and UVs when needed. Solaris and USD contexts make it straightforward to package variants and connect to real-time engines; Houdini Engine supports hand-off to Unreal or Unity. SideFX documents new modelling and USD improvements in version 20, which are relevant when processing large lattices consistently [3], [9].
A hybrid is often best, Houdini for heavy lattice operations and batch export, Grasshopper for designer-friendly editing and last iteration. Exchange via USD layers or GLB for the viewer.
Treat parameters as a versioned contract. Record scan units, sock thickness, arch support scale; activity type, mass, cadence, session minutes, cushioning preference; style preset and cosmetic options; lattice family and grading flags; and export resolutions. Seal each export with a manifest JSON that stores all inputs plus software and component versions. This governance reduces ambiguity when comparing two prints with small changes. Adopt semantic versioning for preset libraries so that design, QA, and print vendors can reproduce outcomes precisely.
Include four layers of checks:
Common risks include noisy scans, unstable lattices at the limit of printability, and over-fitting to a single activity case. Mitigate with scan preflight, proxy previews with simplified lattices, and guardrails on minimum features. For fit variance between left and right, support separate scans rather than mirroring. Address accessibility and inclusion by offering presets that consider orthotic inserts, wider toe boxes, and alternative closure systems. Record data handling practices clearly when using personal scans; store only what is required for geometry generation and delete raw scans on request once builds are complete.
A robust generator produces a watertight midsole and upper, passes automated checks, exports a GLB under 35 megabytes with responsive web preview, and an STL that slices without repair. The link between inputs and outputs is auditable through the manifest. The printed result matches the scan within tolerance and shows pressure reductions consistent with activity intent. The workflow is teachable to designers and engineers without specialisation in lattice mathematics, while providing technical levers for those who need them.
If your team already uses Rhino or Houdini, you can assemble a first version rapidly by adopting the tool recommendations cited here, then iterating on presets as wear data accumulates. For publication-grade work, bring QA forward, record all thresholds and decisions, and build a repeatable chain from scan intake to signed-off print.