PEG Compounds (Polyethylene Glycols)
PEG ingredients themselves are low-hazard but are produced via ethoxylation, which generates 1,4-dioxane and ethylene oxide as contaminants. Purity depends on supplier-level vacuum stripping.
Polyethylene glycols, commonly abbreviated as PEGs, are synthetic polymers widely used in cosmetics, personal care products, and pharmaceuticals as humectants, emulsifiers, and penetration enhancers. PEG compounds themselves are considered low-hazard ingredients and are permitted by the FDA for use in cosmetics and drugs. However, the manufacturing process used to produce PEGs—a chemical process called ethoxylation—can generate two concerning contaminants: 1,4-dioxane and ethylene oxide. These contaminants are not intentionally added but rather arise as byproducts during production. The presence and concentration of these impurities depend heavily on supplier-level manufacturing practices, particularly the use of vacuum stripping and other purification techniques to remove residual contaminants. The health significance of PEG contamination centers on the properties of 1,4-dioxane and ethylene oxide rather than PEGs themselves. According to the National Toxicology Program (NTP), 1,4-dioxane is reasonably anticipated to be a human carcinogen, and ethylene oxide is classified as a known human carcinogen by the International Agency for Research on Cancer (IARC). While the levels of these contaminants in finished cosmetic products are typically low, repeated dermal exposure through personal care products used daily raises concerns about cumulative exposure, particularly for vulnerable populations. The Environmental Working Group (EWG) has documented that PEG-contaminated products can contain measurable levels of 1,4-dioxane, though the actual risk depends on both the concentration present and frequency of use. Regulatory approaches to PEGs differ significantly between regions. In the United States, the FDA permits PEGs in cosmetics and does not mandate contaminant testing or disclosure on labels, though the agency does monitor for safety issues. The European Union takes a more precautionary stance: while PEGs are permitted in cosmetics under EU Regulation 1223/2009, the European Commission's Scientific Committee on Consumer Safety (SCCS) has flagged purity concerns and recommends that PEG ingredients be produced with methods that minimize 1,4-dioxane and ethylene oxide residues. Several EU member states and California have implemented stricter standards for allowable residue levels in cosmetic ingredients. The Cosmetic Ingredient Review (CIR) panel has evaluated PEGs and concluded they are safe as used in cosmetics when manufactured to appropriate purity standards, underscoring that the safety profile depends critically on production quality. For consumers seeking to minimize potential exposure, several practical steps are available. First, look for products labeled as "PEG-free" if you wish to avoid this ingredient class entirely; many natural and clean beauty brands offer alternatives using different emulsifiers and humectants such as glycerin, hyaluronic acid, or plant-derived alternatives. Second, when PEGs are present, prioritize products from manufacturers that publicly commit to stringent supplier audits and contaminant testing, particularly those meeting EU cosmetic standards or California requirements. Third, reduce the number of products containing PEGs in your daily routine, as this lowers cumulative exposure. Reading ingredient lists carefully—PEGs appear as "PEG-3," "PEG-6," "PEG-40," and similar designations—allows you to track your exposure. While PEGs are not banned and pose minimal risk at typical use levels when properly manufactured, the availability of alternative ingredients and the regulatory preference for low-contaminant formulations make it reasonable for cautious consumers to seek PEG-free options, particularly in products used frequently or on sensitive skin.
No implicated brands on record
We only list brands once we have a primary-source link tying them to this issue. Nothing on file yet.