Sour gas is natural gas that contains significant hydrogen sulfide. It is one of the most consequential distinctions in gas production because it dictates the safety precautions, materials, and processing a field requires before the gas can be sold.
Sour Gas in one line: Sour gas is natural gas containing appreciable amounts of hydrogen sulfide (H2S), and often carbon dioxide. It is corrosive and toxic and cannot enter pipelines or be sold until the H2S is removed. Gas with little or no H2S is called sweet gas. The line between them is set by pipeline and sales specifications, commonly around 4 ppm H2S.
Whether a gas is sour or sweet is defined by its hydrogen sulfide content relative to the specification it must meet. U.S. pipeline sales specifications typically cap H2S at about 4 ppm (roughly a quarter grain per 100 standard cubic feet), so gas above that must be treated. Gas at or below the limit is sweet and can be sold; anything meaningfully above it is sour.
Sourness is a spectrum. Some reservoirs carry only a few ppm of H2S; others contain several percent, and a handful worldwide exceed 15 to 30 percent H2S, which is extraordinarily hazardous. Carbon dioxide often accompanies H2S; together they are called acid gas because they form acids in water and are removed in the same treating step.
Two problems make sour gas demanding. First, safety: H2S is acutely toxic, so sour fields require gas detection, personal monitors, escape breathing apparatus, and emergency planning throughout drilling, production, and processing. Second, corrosion: wet H2S attacks ordinary carbon steel and can cause sulfide stress cracking and hydrogen-induced cracking, sudden brittle failures of pressurized equipment.
Because of the cracking risk, sour service requires special materials selected under standards such as NACE MR0175 / ISO 15156, controlled-hardness steels, and corrosion inhibition. Handling sour gas therefore costs more in metallurgy, monitoring, and procedure than sweet gas at every stage from wellhead to plant.
Before sour gas can be sold, the acid gases are removed in a process called sweetening, most commonly with an amine unit that absorbs H2S and CO2 into a circulating solvent and then strips them back out. The concentrated acid gas stream is then routed to a sulfur recovery unit, often a Claus plant, that converts H2S into elemental sulfur, or is otherwise disposed of by acid gas injection.
The result is pipeline-quality sweet gas plus a sulfur or acid-gas byproduct. In the field, sour operations lean heavily on continuous monitoring, H2S detector readings, treating-unit performance, and inlet gas quality, so that any upset that lets H2S slip downstream or accumulate on site is caught immediately.
There is no universal number; it depends on the specification the gas must meet. In practice, U.S. pipeline sales contracts commonly limit H2S to about 4 ppm, so gas above that threshold must be sweetened and is treated operationally as sour. Some definitions use higher processing thresholds.
Not by itself. Sourness specifically refers to hydrogen sulfide. Carbon dioxide is an acid gas that often accompanies H2S and is removed in the same treating step, and high-CO2 gas is corrosive, but gas is labeled sour because of its H2S content.
Operators continuously watch H2S detectors, amine-unit parameters, and inlet gas quality. A cloud SCADA system such as Merobix can consolidate those signals from field controllers over Modbus, DNP3, or OPC UA so remote engineers monitor treating performance and site H2S status, while the safety trips remain in dedicated local hardware.
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.