Waterproofing is architecture, not a finishing step
You cannot add water resistance at the end of a project. Sealing is a combination of precise geometry, material selection, controlled closing force, and systematic testing — and the difference between an IP65 requirement and an IP67 requirement can change the entire architecture of the product. If you are building a waterproof prototype, the sealing strategy has to be decided while the enclosure is still a sketch.
The short version: choose the rating from the real use case, design a proper sealing interface rather than adding a rubber ring at the end, build the prototype in a material dense enough to test the principle, and prove it with repeatable tests long before you commit to a mold.
What an IP rating actually promises
An IP code has two digits. The first covers solids and dust: 5 means dust-protected, 6 means fully dust-tight. The second covers water, and that is the one that sets the difficulty of your project.
- IPX4 — splashing from any direction. Appropriate for kitchen and bathroom products, and reachable with modest design effort.
- IPX5 and IPX6 — direct water jets at increasing pressure. Relevant to anything that gets hosed down, washed, or lives outdoors in rain.
- IPX7 — temporary immersion to roughly one meter. Important subtlety: passing immersion does not imply passing a pressure jet. They are different tests stressing different parts of the seal.
- IPX8 — continuous immersion under conditions the manufacturer defines and publishes.
Pick the rating your product will genuinely encounter, not the one that reads best on a spec sheet. Every step up adds part cost, complicates assembly, and adds test burden. Our full reference on IP ratings covers the test conditions behind each digit.
Sealing methods that hold up in the real world
- An O-ring in a properly designed gland. The most reliable answer for anything that opens and closes repeatedly — provided the groove is dimensioned for the right compression and the sealing surfaces are finished correctly. The design rules are in our guide to O-ring selection and gland design.
- Flat or form-in-place gaskets. For large lids and flat trays where a round cross-section is impractical. Requires even bolt spacing so compression is uniform.
- Ultrasonic welding or adhesive bonding. Permanent sealing for housings never meant to open. Inexpensive per unit in volume, but the joint has to be designed for it — see ultrasonic welding of plastic parts.
- Potting. Flooding the electronics in resin gives excellent protection and is effectively irreversible, which makes debugging a prototype painful. Useful for a final configuration, awkward mid-development.
- A vent membrane. Equalizes internal and external pressure so temperature swings do not pull moisture through the seals. Often the cheapest fix for a product that mysteriously fogs or drips inside.
- Sealed cable entries and connectors. The single most common failure point. A cable entering through an unsealed hole with no proper gland or strain relief cancels every other measure in the list.
All of it starts from how the housing itself is laid out — split lines, closing direction, screw placement, rib stiffness so the lid does not bow between fasteners. Our guide to electronics enclosure design covers those decisions in order.
Why your printed prototype leaks, and what to do about it
FDM printing builds a part layer by layer, and the microscopic gaps between layers wick water through a wall that looks flawless. That is a property of the process, not evidence that your design is wrong.
Options at prototype stage: print in SLA resin, which produces a far denser and effectively non-porous wall; seal an FDM part with epoxy or a penetrating lacquer; use cast urethane, which behaves much more like the eventual molded material; or machine the critical sealing components from solid stock. The trade-offs between the main printing routes are compared in FDM versus SLA.
The key mental shift: a leaking printed prototype does not predict failure of the molded part, and a printed part that passes does not guarantee the molded one will. At prototype stage you are testing the sealing principle — geometry, gasket, compression, cable entry — not that specific piece of plastic.
How to test for leaks without ruining hardware
- Immersion with an internal witness. Put blotting paper or indicating silica gel inside, immerse per the target rating, then open it. Water ingress becomes obvious and you can tell where it entered.
- Air pressure decay. Pressurize the housing slightly and watch for pressure drop over time. Fast, dry, repeatable, and it finds leaks without putting live electronics near water. This is the test to use during iteration.
- Controlled spray. Reproduce the real scenario — shower, garden hose, washdown — at the level your rating claims, from the angles the standard specifies.
- Thermal cycling before and after. Heat and cool the sealed unit, then re-test. Many seals only fail after the housing has expanded and contracted a few times.
Fold these into the broader test plan rather than running them once — the framework is described in our guide to reliability testing for a new product. Document every failure. Each leak tells you something specific about the design.
Water is only one of the enemies
If the product lives outdoors, other stresses are waiting: ultraviolet radiation that chalks and embrittles plastics, temperature extremes that change gasket compression, condensation cycles, salt, and dust that scores sealing surfaces. Specify UV-stabilized materials and gasket compounds rated for the temperature range from the start, because swapping a material late usually changes the fit of the seal.
If you are designing a sealed product now, involve an engineer while the geometry is still cheap to change. More guides on building and validating physical models are collected on our prototyping hub.
Need a waterproof prototype that will still pass once it is tooled? Reach out through our contact form and the Projects House team will help you set the right rating, design the sealing interface, and build a test plan that proves it.