API SP vs API SQ

Standards Technical Guide

API SQ is the gasoline-engine oil service category introduced with the ILSAC GF-7 generation in March 2025. API SP was introduced with GF-6 in May 2020. Both address modern gasoline engines, but SQ raises selected performance requirements for areas such as aged-oil low-speed pre-ignition protection, timing-chain wear, deposits, fuel economy, emissions-system protection, and low-temperature behavior.

For automotive gasoline categories, API states that the latest category includes the performance properties of earlier categories. That supports backward service in many applications, but viscosity and manufacturer requirements still control the final choice.

API SP and API SQ comparison

Why API SQ was introduced

Engine hardware and test requirements continue to evolve. Turbocharged gasoline direct-injection engines can expose oils to high temperature, deposit stress, chain wear, and low-speed pre-ignition. Oil also ages in service, which can change its ability to control those problems. The SQ generation updates the category around current test methods and performance targets.

Fuel economy and emissions-system durability remain part of the broader licensing framework when the oil also carries the applicable Resource Conserving or ILSAC claim. API SQ alone and API SQ Resource Conserving are related but not identical label statements.

Aged-oil LSPI protection

LSPI is abnormal combustion that can occur before the intended spark event, especially under low-speed, high-load operation in certain boosted direct-injection engines. API SP introduced specific LSPI protection. API SQ extends the focus to performance after the lubricant has aged.

A category claim does not repair an engine problem or override manufacturer software, fuel, maintenance, or operating guidance. It shows that the licensed oil completed the defined category requirements.

API marks and licensing

The API Service Symbol, commonly called the Donut, communicates the licensed service category and viscosity grade. ILSAC-qualifying oils can also display the relevant API certification mark. The marks are controlled program identifiers rather than decorative claims.

Consumers can check the API online directory when licensing matters. Product names and viscosity grades should match the listing because one brand may sell both licensed and non-licensed products.

Backward compatibility and limits

API gasoline categories generally follow a backward-service principle. An API SQ oil can therefore provide the performance of earlier API S categories. That statement does not allow any SQ viscosity grade in any older engine. Some engines need a specific viscosity, high-HTHS formulation, European OEM approval, or specialty chemistry.

Classic engines, racing applications, unusual fuels, and manufacturer-specific extended drains can require a different decision process. The owner documentation remains the authority for viscosity and OEM approvals.

How to verify the correct requirement

Begin with the equipment documentation rather than a product label. Record the model year, engine or component code, market, emissions configuration, and service category. Then copy the complete viscosity and performance requirement exactly as written. A familiar grade, family name, or nearby specification number is not enough because revisions can change test limits, permitted viscosity ranges, and hardware compatibility.

1. Confirm the application. Use the owner's manual, service information, or manufacturer lubricant chart for the exact equipment.
2. Separate viscosity from performance. A viscosity grade describes rheology. An API, ACEA, JASO, ISO, or OEM code adds a different set of requirements.
3. Check the complete product claim. Compare the exact code and revision on the current technical data sheet. Do not rely only on a marketplace title or bottle photograph.
4. Distinguish approval from suitability. “Approved,” “licensed,” “meets,” and “recommended for” can represent different verification routes. Check an official directory when formal approval is required.
5. Resolve conflicts conservatively. If the manual, a supplier chart, and a seller listing disagree, ask the equipment manufacturer or a qualified service provider before substituting the lubricant.

For API SP vs API SQ, documentation dates matter. Standards and approved-product lists change, while old data sheets can remain online. Save the source date when the decision affects warranty coverage, fleet policy, extended drains, or expensive equipment. This simple record shows which information supported the service decision.

Common interpretation errors

• Assuming a higher number is automatically better. Specification numbers identify requirements; they are not universal quality rankings.
• Using viscosity as the only filter. Two oils in the same SAE or ISO grade can have different additive chemistry, licenses, friction behavior, emissions compatibility, and intended applications.
• Treating every newer standard as backward compatible. Some categories include earlier performance, while others apply to restricted viscosity grades or specially designed hardware.
• Ignoring service conditions. Temperature, fuel sulfur, contamination, load, duty cycle, drain interval, and aftertreatment hardware can change the correct choice.
• Reading one property as a formulation score. HTHS viscosity, viscosity index, base-oil group, zinc concentration, or sulfated ash can be important, but no single number describes total lubricant performance.

Documentation and condition monitoring

A sound lubricant decision records more than the product name. Keep the data-sheet revision, viscosity grade, specification wording, batch or purchase information when relevant, installation date, service interval, and equipment hours. For fleets and industrial assets, note ambient range, normal operating temperature, duty cycle, fuel or process exposure, filtration, make-up volume, and any change from the previous lubricant. This record separates a deliberate engineering choice from an undocumented substitution.

Used-oil analysis can show trends in viscosity, oxidation, contamination, wear debris, additive elements, fuel dilution, water, soot, or particle count. However, a laboratory result does not retroactively approve an unsuitable specification. Analysis works best after the correct lubricant has been selected and a representative baseline has been established. Sampling location, machine temperature, flush volume, container cleanliness, laboratory method, and consistent service hours all affect the comparison.

When a result changes, investigate the system rather than blaming one property immediately. A viscosity decrease may involve fuel or solvent dilution, mechanical shear, mixing, or a sampling issue. An increase can reflect oxidation, soot, evaporation, contamination, or the wrong top-up fluid. Combine the result with temperature, pressure, filter condition, consumption, alarms, maintenance history, and operating changes before deciding on corrective action.

Review the program after major repairs, software updates, emissions-system changes, fuel changes, or a move to a different climate or duty cycle. A lubricant that was correct for the previous configuration may need renewed confirmation. Controlled change management also prevents an emergency top-up or supplier substitution from silently becoming the long-term specification.

Frequently asked questions

Official resources