Should specify conformal coating for reliability and when is it necessary?

If you build electronics for the real world, you’ve seen the same headache: the board passes in the lab, then it goes to a humid warehouse, a salty coastal site, or a dusty cabinet, and suddenly you’re chasing leakage, random resets, or that dreaded NFF (No Fault Found) return.

Conformal coating can help a lot. It can also create new problems if you write the spec the wrong way. Below is a practical way to decide when you should specify coating for reliability, and how to write it so your supplier doesn’t “interpret” your intent.

You can also align this with a fast-turn, high-mix supply chain like a China B2B PCB factory that does prototyping and volume PCBA with strict QC, like what we describe across our homepage, PCB fabrication, and PCB assembly pages.

You should decide by “use environment,” not by habit

Coating isn’t a fashion choice. Treat it like a reliability control tied to environmental stress.

High humidity and condensation

If your product sees high RH, quick temperature swings, or any chance of condensation, you’re basically inviting moisture to sit on the board. That’s when you get surface leakage, corrosion, and sometimes dendrites that slowly grow until they short something.

Typical scenarios

• Outdoor boxes, rooftop gear, smart agriculture controllers
• Cold-to-warm cycles (shipping container → warm indoor install)
• Equipment near HVAC, water lines, or cold plates

Salt fog and corrosive gas

Salt and corrosive gases don’t need much time. They attack exposed metal and can turn tiny residues into bigger failures fast.

Typical scenarios

• Coastal telecom, marine electronics
• Industrial plants with chemical vapors
• Power cabinets in harsh sites

Dust and conductive debris

Dust sounds harmless until it mixes with humidity or becomes conductive (metal dust, carbon, brake dust). Then it becomes a “free resistor” across pins.

Typical scenarios

• Factory floor controls, mining, construction equipment
• Motor drives and cabinets with airflow and filters that aren’t maintained

You should specify coating more when failure is expensive

This is the simple rule: the harder it is to service, the more you should lock down reliability controls. If your unit sits in the field for years, or if an RMA means downtime for an entire line, coating becomes a real lever.

Typical scenarios

• Remote monitoring nodes, industrial gateways
• Medical or safety-related devices (where intermittent faults are unacceptable)
• Customer products with high RMA penalty and brand risk

If you’re building for OEMs and EMS partners, write the requirement clearly so it survives the handoff from design to procurement to manufacturing. Our services and capabilities pages reflect that “design intent → build intent” workflow.

High voltage and high density need extra care, but don’t treat coating as “primary insulation”

Coating can improve surface insulation and help reduce arc risk on tight layouts. That said, it’s not a magic shield. You still need solid creepage/clearance, good layout, and the right material stack.

Where coating helps

• HV sections with contamination risk
• High-density boards where spacing is tight and the environment is rough

Where coating won’t save you

• Poor spacing, sharp points, or layout that violates your safety design rules
• Designs that rely on coating to “fix” basic insulation gaps

If your board has dense connectors or fine pitch, bring that up early during DFM so you don’t end up with trapped coating in places you can’t clean or inspect.

Don’t write “coat everything”: define coated zones and keep-out zones

This is where many specs go wrong. “Full coat” sounds safe, but it can ruin testability and create hidden defects.

Connectors, test pads, and contact areas

You usually want keep-out areas for:

• Connectors (especially unsealed)
• Test pads (ICT / flying probe access)
• Ground contacts, spring contacts, press-fit zones
• Heat sink interfaces or areas that must bond

If you skip this, your supplier might mask on the fly, or worse, they won’t mask well. Then you get coating creep into a connector and intermittent contact resistance shows up months later.

This is also where strong process control matters. If you care about outgoing quality gates, you’ll want your coating spec to match your quality expectations, not fight them.

Cleaning and surface preparation decide whether coating helps or hurts

Coating over a dirty board is like painting over oil. It might look fine, then it fails later.

What usually bites teams:

• Flux residues that trap moisture
• Ionic contamination that drives leakage under bias
• Poor adhesion that leads to delamination or “fish-eyes”
• Shadowed areas under tall parts where residues hide

If you’re seeing weird field leakage, don’t just yell “add coating.” First ask: Was the board properly cleaned and dried before coating? A good build plan ties cleaning, inspection, and coating together as one process, not three disconnected steps.

Coating can reduce test access and make rework messy, so plan for it

Coating affects the boring things that keep production stable:

• ICT access: test pins need metal pads
• Rework cycles: removing coating takes time and can damage solder mask
• Thermal behavior: coating can slightly change heat paths or trap heat around hot parts
• Debug speed: lab bring-up gets slower when you’re scraping film off pads

If your product is still in heavy iteration, you may want selective coating or a phased plan: no coating during EVT, then add it when the design stabilizes.

Summary table: what to specify, when it’s necessary, and what problem it prevents

Argument title (use in spec reviews)	What it means in practice	When it’s necessary	What it prevents	Source type (for traceability)
Decide by “use environment,” not by habit	Tie coating to humidity, salt, dust, chemicals	Outdoor/industrial/condensing sites	Leakage, corrosion, dendrites	Industry reliability practice + coating vendor guidance
Specify more when failure is expensive	Treat coating as insurance for high RMA pain	Remote install, long-life, mission-critical	NFF returns, downtime risk	OEM/EMS quality planning practice
High voltage and high density need extra care	Coating supports insulation, not replaces it	HV sections in harsh environment	Surface tracking, arc risk	Safety design practice + HV layout rules
Don’t write “coat everything”	Define coat zones and keep-out zones	Boards with connectors/test points	Connector contamination, blocked test	IPC-style workmanship guidance + DFM practice
Cleaning and surface prep are mandatory	Add cleaning/dry steps before coating	Any coated PCBA	Adhesion failure, ionic leakage	Process engineering practice
Test and rework impact must be planned	Keep pads accessible and plan rework	Early iteration or high debug rate	Slower debug, rework damage	EMS production control practice

What to put in your conformal coating specification

If you want fewer surprises, write these items in plain language:

• Purpose / environment: humidity, condensation, salt, dust, chemical exposure
• Coverage definition: “selective coating” with clear coated zones and keep-out zones
• Keep-out list: connectors, test pads, ground contacts, heatsink interfaces
• Process requirements: clean + dry before coating, plus basic inspection checkpoints
• Rework rules: allowed rework method, and how many rework cycles you expect
• Acceptance criteria: no pooling, no bubbles, no bridging between fine-pitch leads, no coating inside connectors

If you want this to run smoothly from prototype to mass production, align it with your manufacturing flow. That’s the same reason we keep our site organized around PCB fabrication, PCB assembly, and overall capabilities—it keeps reliability requirements tied to real process steps.

Real-world scenarios that usually justify coating

• Industrial control board in a cabinet: Dust + humidity + long uptime. You want selective coating, strong keep-outs for terminal blocks, and test access for ICT.
• Connector-rich controller: High risk of coating wicking into connectors. You want strict keep-outs and a masking plan.
• Outdoor IoT node: Condensation events matter more than average humidity. You want coating plus attention to cleanliness.
• High-density, fine-pitch board: Coating can help, but only if the process can avoid bridging and can inspect coverage.
• Serviceable spare-part boards: You might choose partial coating so field repair doesn’t turn into a scraping job.

If you’re collecting reliability notes and DFM tips for your team, you can also publish or organize them under your blog so procurement and engineering stay on the same page.

Closing thought

Conformal coating works best when you treat it like a controlled process, not a last-minute add-on. If you define when it’s necessary, lock down where it goes, and protect test/rework, you’ll cut down on field noise and stop paying for preventable RMAs.

When you’re ready to turn those notes into an executable build spec, the fastest path is to package the coating intent together with your PCBA flow and quality gates. If you want a quick handoff point for that, use the contact page so your team can attach drawings, keep-out screenshots, and acceptance criteria in one thread.