Feature

One ingredient an AI looks at when it makes a judgment

  • Intro
  • 6 min read
  • 3 diagrams

Key points

  • A feature is one ingredient an AI looks at when it makes a judgment. It's the values that summarize a single thing down to a handful of numbers.
  • Choosing what counts as a feature largely decides performance. No good ingredients, no good judgment.
  • Load in values that have nothing to do with the judgment and they can get in the way instead. The model can mistake a coincidence for something real.
  • Features are the question, labels are the answer key. A feature is what the AI looks at; a label is the answer known in advance.
  • These days, with photos, sound, and text, deep learning finds a good share of useful ingredients on its own straight from raw material, without a person refining them first.

The analogy

Scan an item at a convenience store checkout and a string of values pops up on the screen: the price, the weight in grams, which category it belongs to, whether it needs refrigeration, and how long until it expires. A single product gets summed up in a handful of values like these. Each one of those values is a feature.

The register never sees the actual product. Whether the packaging looks nice, or whether it sits somewhere shoppers' hands reach easily, never shows up on the screen. It can only show what's been registered, and anything that wasn't registered might as well not exist.

Deciding what gets registered is a person's call. Managing inventory calls for weight and storage method; tracking sales calls for price and category. Change the goal, and the values worth keeping change with it.

In detail

Choosing what to look at shapes performance

The same material can produce very different results depending on which values get pulled out of it. To estimate a used car's price, the model year and the mileage are essential, while the license plate number is completely useless. Leave out a value you actually need, and no method, however good, will get you there.

Values don't always get used as-is; they're often reshaped first. Age is more useful than a birth date; the number of years since a car left the factory is more useful than the release date and today's date side by side. Building useful values like these out of raw material is called feature engineering.

Back when machine learning was first catching on, this work was most of the job. Someone who knew the subject well, picking out what to look at, mattered more than swapping in a different model.

Values with no connection can get in the way

It seems like adding more values should help, but it doesn't work that way. Mix in a value that has nothing to do with the judgment, and the model can pick up on whatever coincidental pattern showed up in that value. If, purely by chance, the cars with higher plate numbers in the training data happened to be pricier, the model learns that relationship as if it were real.

A value like that holds up only in the training material and tends to collapse once new material comes in. That's why, when choosing features, the bigger concern is usually trimming values that don't help rather than adding more.

Overlapping values cause trouble too. Put height in centimeters into the mix and then add it again in meters, and it tells the model nothing new while adding to the computation.

Features and labels sit in different places

Picture one record as a row in a table: the earlier columns are features, and the last column is the label. A feature is the question the model has to work out an answer to; a label is the answer known ahead of time. Sometimes a person attaches it, and sometimes it comes from records, such as sales figures.

Both are needed for training — the answer produced from the features gets checked against the label, and the numbers get adjusted by however much they missed. Once the model is actually in use, though, there's no label. New material arrives with features only, and figuring out the answer is the model's job.

Mix this up and it causes a real mistake. Slip a value into the features that can only be filled in once you already know the answer, and test scores look great while the model turns out useless in practice, since that value can't be had in the real world.

Everything has to become a number before it can be computed

A model can't work with letters or pictures as they are. Whatever the feature, it eventually has to turn into a number. A value like refrigerated-or-not gets spread across present-or-absent slots; a value with no natural order, like region or category, gets the same treatment, split across separate slots.

In many models, values that differ wildly in scale need their scale matched too. If one value moves between 0 and 1 while another swings in the hundreds of thousands, the larger one ends up dragging the whole judgment along with it. So values are often rescaled to a similar range beforehand. Some methods, like tree-shaped models that split on the order of values alone, aren't affected by scale.

These days the model finds its own ingredients

This picture has shifted a lot as deep learning has spread. Nobody has to tell the model what to look for in a photo — a model built from stacked layers builds useful ingredients directly out of the raw pixels, layer by layer. Early layers pick out something simple, like lines and edges; later layers catch chunkier shapes, like a wheel or the outline of a face.

That hasn't erased the human role, though. With table-style data in particular, features a person has shaped still often carry a lot of weight. What material to feed in, and what values to leave out entirely, are still calls a person makes. Values like age or region, in particular, which can steer the model toward bias, need careful judgment about whether to include them at all.

More precisely

A feature is one input variable representing a single sample. A sample becomes a bundle of numbers listing several features side by side, and that bundle is what goes into the model as input. How many features there are sets the length of that bundle, and the longer it gets, the more the data spreads thin, which sharply raises how much data is needed to hit the same level of performance. That's why overlapping values sometimes get merged into one to shorten the bundle.

The analogy breaks down in a couple of places too. The values on a convenience store screen read independently of one another, but the features a model uses are tangled together and act jointly. Weight alone means nothing, but set alongside price, whether the item is a good deal or not comes into view. And the values on the screen carry names because they were made for a person to read, while the ingredients deep learning builds partway through often come out as number bundles that a person can't put a name to.

Try it yourself

Common misconceptions

  • It's easy to think that adding more features makes a model more accurate, but actually mixing in unrelated values can teach it a coincidental pattern, and the risk of collapsing on new material goes up.

  • It's easy to think features and labels are basically the same thing, but actually a feature is the material a model looks at, and a label is the answer known in advance.

  • It's easy to think deep learning means nobody needs to worry about features anymore, but actually deciding what to include and what to leave out is still a person's call.

One-line summary

In short

A feature is one ingredient an AI looks at when it makes a judgment, and what gets chosen as an ingredient decides what the model can ever learn to recognize.

Spotted an error or have a better analogy? Suggest an edit · Last updated 2026-10-17