Alkali burn is one of the most common reasons coatings fail prematurely on concrete slabs, masonry walls, tilt-up panels, and other cementitious substrates. It occurs when soluble salts and high-pH moisture migrate to the surface and react with the coating, causing discoloration, efflorescence, blistering, or complete paint adhesion failure. Properly identifying, treating, and preventing alkali burn is essential for achieving a durable, professional-grade finish on any concrete painting project.
Understanding the Root Cause of Alkali Burn
Fresh concrete typically has a pH of 12–13 due to cements inherent alkalinity. Over time, this pH naturally drops as the slab cures and carbonates, eventually reaching a paintable range of roughly pH 8–10. When concrete is coated too early, or when moisture intrusion continues after the initial cure, alkaline salts dissolve and move to the surface. As they accumulate, the salts can burn or stain primers and topcoats, leaving the appearance mottled, chalky, or blotchy.
High moisture vapor drive also intensifies the issue. Even older slabs can show alkali burn if there is groundwater pressure, improper vapor barriers, or hydrostatic conditions. For this reason, both pH and moisture testing are crucial diagnostic steps prior to painting.
Inspecting and Testing for Alkali Burn
Professionals typically start with a visual inspection: signs include white, powdery efflorescence; brownish or yellowish staining beneath coatings; or localized peeling in a crystalline pattern. To confirm alkalinity levels, a pH pencil or distilled-water spot test is used. Any reading above pH 10 indicates elevated alkalinity and requires corrective measures. Moisture testing using a calcium chloride test, in-slab probes, or a high-quality moisture meter determines whether excessive vapor transmission is contributing to the issue.
Surface Preparation Procedures
Solving alkali burn is a combination of cleaning, neutralizing, and ensuring moisture control. Begin by removing all compromised coatings with mechanical methods such as abrasive blasting, diamond grinding, or aggressive power washing. The surface must be free of efflorescence, chalk residue, and loose paint before treatment. Cleaning agents, typically mild acid washes such as diluted muriatic acid or phosphoric acid solutions, are used to neutralize alkalinity. These should be applied strictly according to manufacturer instructions, followed by thorough rinsing until runoff water is clear and pH tests confirm acceptable levels.
In areas where acid washing is not suitable, proprietary alkali-resistant cleaners and neutralizing agents are available. These products reduce pH without the risks associated with strong acids. After rinsing and drying, conduct additional pH checks to ensure the substrate is within specification.
Moisture Management
Even if the surface is neutralized, persistent moisture problems must be addressed to prevent recurring alkali burn. Solutions may include installing or repairing vapor barriers, correcting drainage around the structure, sealing cracks, or applying moisture-mitigation systems such as epoxy moisture-blocking primers. The substrate must be dry according to the coating manufacturer’s recommended moisture limits before any primer is applied.
Priming and Repainting
Once the concrete is neutralized and dry, use an alkali-resistant primer specifically designed for high-pH substrates. Acrylic masonry primers, epoxy primers, and elastomeric bonding primers are frequently specified for these conditions. After priming, apply high-quality exterior or masonry-grade coatings with proven resistance to alkali attack. Following the manufacturer’s recoat windows is essential for long-term adhesion.
Handling alkali burn on concrete before painting requires a structured, diagnostic approach: confirm pH, evaluate moisture, remove damaged coatings, neutralize the concrete, allow proper dry time, and apply alkali-resistant primers. When executed correctly, these steps ensure coatings bond properly, resist salt migration, and maintain appearance for years, reducing callbacks and safeguarding the project’s longevity.
