Skip to content

Steel and Metal Surface Defect Data

By Noah Loul · Reviewed by Noah Loul · Updated

  1. 01Your data spec
  2. 02Matched to businesses
  3. 03Rights and samples reviewed
  4. 04Licensed delivery
How it works with SourceX: Your data spec → Matched to businesses → Rights and samples reviewed → Licensed delivery.Illustrative

Short answer

Steel and metal surface defect data comes from public benchmarks and from mills, processors and parts makers. Public sets such as NEU (1,800 images, six defect classes) are small and carry research licenses; production archives hold more variety but need rights review, relabeling and metadata. Neither shows robot handling, and benchmark scores rarely transfer to a new surface, finish or camera.

Why metal surfaces have their own data problem

Metal inspection mixes two situations that need different data. Flat products such as hot-rolled strip, sheet and plate are scanned continuously, and defects are texture-like: scale, pits, scratches, inclusions. Machined and fabricated parts are inspected as discrete units with geometry, edges, holes and finish variation, and defects include scratches, dents, burrs and contamination.

Because reflectance and finish dominate appearance, the same defect looks different under different lighting and surface treatment. That is why public benchmarks are valuable for method comparison and limited for deployment. The overview of image dataset sourcing is in sourcing defect image datasets; this page adds the metal-specific route. Cluster context is at inspection and the humanoid data section.

Public benchmarks and what they contain

DatasetWhat its publication supportsTypical useWatch for
NEU surface defect databaseSix hot-rolled steel strip defect types: rolled-in scale, patches, crazing, pitted surface, inclusion, scratches; 1,800 grayscale images; 300 per class; 200x200 pixels (Song)Classification baselinesSmall images, balanced classes unlike real rarity
KolektorSDD2Over 3,000 images with several defect types; evaluated alongside KolektorSDD, DAGM and Severstal (Božič et al., 2021)Segmentation and weak-supervision studiesSingle product family
MPDDMetal-part images captured under complex production conditions with anomaly-free training images and pixel-precise masks in six categories: bracket_black, bracket_brown, bracket_white, connector, metal_plate, tubes (Jezek et al., 2021)Anomaly detection on partsFew categories

These sets are useful as baselines and for checking a pipeline. They are not a substitute for data from your own material and finish. A model trained on 200x200 grayscale crops of strip surface has limited relevance to polished machined brackets, and a model that scores well on a balanced benchmark may behave differently when defects are rare.

The license matters. Anomalib documentation states that MPDD is released under CC BY-NC-SA 4.0 (Jezek et al., 2021), and the MVTec AD benchmark carries the same license (Bergmann et al., 2021); a non-commercial license restricts commercial training use. For NEU, check the host page terms before relying on it. This is not legal advice, and a commercial buyer should read each license.

What metal defect data can and cannot support

It can support defect detection, classification and segmentation models, anomaly detection on nominal-only data, and evaluation of inspection systems on specific materials. It cannot show handling: how to present a reflective part to a camera, or how a gripper marks a surface. It also does not show downstream consequence; a visible scratch may be cosmetic or may be rejectable depending on the specification, so images need the disposition link.

Surface defects on metal also depend on process stage. A scale mark before pickling is not the same as after. Record the stage.

Preparing metal imagery for use

Before a metal image set is ready for training or evaluation, expect several steps from the data holder or your own team.

Tile or crop with care. Continuous strip images are cut into tiles. Tiling that splits a long defect across tiles creates partial labels. Decide whether labels are per tile or per defect and keep the mapping to the original coil position.

Separate by material identity. Images from the same coil, heat or machining batch share texture and noise. Keep them in one split to avoid leakage; see leakage in defect datasets for the general mechanism.

Relabel to your classes. A producer's codes reflect its customers' specifications. Mapping them to your list may merge or split classes, and the mapping should be documented.

Record surface condition. Oil film, scale, rust bloom and handling marks change appearance without being defects. Ask whether they were annotated as distractors.

Private supply: who holds metal defect imagery

Illustrative package for a metal defect request

Illustrative; values are synthetic.

ElementExample specification
Material and finishCold-rolled steel, oiled; or machined aluminum, bead-blasted
Defect classesBuyer's list of 6-10, mapped to supplier codes
Image typeLine-scan strips or area-scan tiles, 16-bit if available
LabelsImage-level class plus boxes; masks on a held-out subset
SplitsBy coil, lot and week; no shared parts across splits
MetadataLighting, camera, scale, line speed, process stage
Normal dataDefect-free tiles from the same lots
DispositionAccept, downgrade, scrap, with reason

Evaluating an offer

Distribution realism. Ask for the real class frequencies. A set with equal counts per class has been curated, which is fine for training classifiers but hides the imbalance you will meet in operation; see rare defects and class imbalance.

Label authority. Who judged the defect, with which specification? Surface defect names vary between mills.

Cross-line behavior. Hold out an entire line or coil batch and measure the drop. Performance differences across lines are routine; see domain shift across lines.

Cleanliness. Oil, dust and fingerprints produce false positives. Ask whether cleaning state is recorded.

Limitations and extra preparation

Metal surface imagery is tied closely to the material, finish and optics that produced it. A dataset of hot-rolled strip says little about machined aluminum or brushed stainless steel, and glare, oil films and coolant residue change appearance from one shift to the next. Class definitions vary between plants: what one quality team calls a scratch another calls a handling mark, and severity thresholds are often local customer agreements rather than written rules, so check the applicable specification for each source. Defect classes are usually imbalanced, and the rarest ones are often the ones that matter most.

The data contains no information about how a robot should pick, orient or present a part, so it supports inspection and recognition, not manipulation. Plan for extra preparation: harmonizing the class list across suppliers, recording the finish and lighting per image, re-labeling a sample to check consistency, removing customer part numbers or stamped marks where they are sensitive, and splitting by part, coil or lot rather than by image so that near-identical views do not leak between training and evaluation.

Questions to ask suppliers

  1. Which surface inspection system or camera setup captured the images, and at what resolution and line speed?
  2. What material grade, finish and process stage do the images cover?
  3. How were defects labeled, and by whom, against which specification?
  4. What fraction of images contain no defect, and how were they selected?
  5. Can you split by coil, lot or production week?
  6. Do images show customer part geometry or markings that need approval?
  7. Are original, uncompressed images available?
  8. What dispositions and costs were recorded against defective items?

Discuss your requirements

If you need metal surface defect imagery from US manufacturers, describe the material, finish, defect classes and permitted uses to SourceX. SourceX reviews the requirement and follows up about potential sources, checks the data and the supplier's licensing permissions, and coordinates licensing and delivery. A request does not guarantee a match.

Tell SourceX what your evaluation set needs to cover

Sources

Frequently asked questions

Where does steel and metal surface defect data come from, and how do public sets compare?

Steel and metal surface defect data comes from public benchmarks and from mills, processors and parts makers. Public sets such as NEU, with 1,800 images and six defect classes, are small and carry research licenses, while production archives hold more variety but need rights review, relabeling and metadata.

Why do metal defect benchmarks not transfer directly to a new surface, finish or camera?

Reflectance and finish dominate appearance, so the same defect looks different under different lighting and surface treatment. A model trained on small grayscale strip crops has limited relevance to polished machined brackets, and benchmark scores rarely transfer to a new surface, finish or camera.

Can public metal defect benchmarks such as MPDD and MVTec AD be used for commercial training?

Public benchmarks such as MPDD and MVTec AD carry CC BY-NC-SA 4.0 licenses, which restrict commercial training use. A commercial buyer should read each license, and check NEU's host page terms, before relying on any of them.

Describe the data your robots need

Describe the tasks, modalities and permitted uses you need. SourceX reviews the requirement and follows up about potential sources; a request does not guarantee a match.

Discuss your humanoid training-data requirements with SourceX
See if you qualify