TF-IDF (Term Frequency-Inverse Document Frequency)

TF-IDF (term frequency-inverse document frequency) is a numerical statistic that measures how important a word is to a single document within a larger collection or corpus, computed as the product of two factors: term frequency (TF), how often the word appears in that document, and inverse document frequency (IDF), how rare the word is across the whole corpus.^[14] The score is high for words that are frequent in one document but rare everywhere else, which makes it a way to rank the most distinctive, content-bearing terms while suppressing common function words such as the and of. Term frequency rewards repeated usage as a signal of topical relevance, while inverse document frequency discounts words that occur in many documents because they tend to be generic and uninformative.^[1] TF-IDF is one of the oldest and most widely used weighting schemes in information retrieval and natural language processing, and despite the rise of dense neural representations it remains a default baseline for ranking, classification, and feature engineering.

The scheme has a long pedigree. The notion of inverse document frequency was introduced by Karen Sparck Jones in a 1972 paper titled A Statistical Interpretation of Term Specificity and Its Application in Retrieval in the Journal of Documentation, whose central argument was that the specificity of a term should be interpreted statistically, as a function of how the term is used across the collection rather than of its meaning.^[1] Gerard Salton and Christopher Buckley consolidated the term-weighting literature in their 1988 paper Term-weighting approaches in automatic text retrieval in Information Processing and Management, where they catalogued the variants of TF and IDF and established empirical guidelines that are still cited decades later.^[2] Salton's earlier vector space model, implemented in the SMART system at Cornell, paired TF-IDF weights with cosine similarity and became the dominant ranking framework for a generation of search systems.^[3] The classical reference textbook is Christopher Manning, Prabhakar Raghavan, and Hinrich Schutze's Introduction to Information Retrieval (Cambridge University Press, 2008), whose chapter on scoring devotes substantial space to TF-IDF and its SMART notation.^[4]

How is TF-IDF defined and calculated?

Let a corpus consist of $N$ documents indexed by $d$, and let $t$ denote a term (typically a word, but possibly a phrase or character n-gram). Two basic statistics are defined.

Term frequency $\text{tf}(t, d)$ counts the number of times term $t$ occurs in document $d$. The simplest definition is the raw count, but several normalizations are common in practice.

Document frequency $\text{df}(t)$ counts the number of documents in the corpus that contain term $t$ at least once. The inverse document frequency is then defined as

$\text{idf}(t) = \log \frac{N}{\text{df}(t)}$

where the logarithm is usually taken base 2 or base 10 (the choice is immaterial because it scales all weights uniformly). The intuition is information-theoretic: if a term occurs in only a small fraction of documents, observing it in a query carries a great deal of evidence about which document is intended, whereas a term that occurs in nearly every document carries almost none.^[8]

The TF-IDF weight is the product

$\text{tf-idf}(t, d) = \text{tf}(t, d) \cdot \text{idf}(t).$

A document is then represented as a vector whose components are the TF-IDF weights of all terms in the vocabulary. Most vocabulary entries do not appear in any given document, so these vectors are extremely sparse and are stored as lists of (term index, weight) pairs.

Worked Example

Consider a corpus of $N = 1{,}000{,}000$ news articles. The word the appears in essentially all of them, so $\text{df}(\text{the}) \approx 1{,}000{,}000$ and $\text{idf}(\text{the}) = \log(10^6 / 10^6) = 0$. The word transformer might appear in $5{,}000$ documents, giving $\text{idf}(\text{transformer}) = \log(10^6 / 5{,}000) \approx 7.64$ in base 2 or $2.30$ in base 10. The word embiggens might appear in only $10$ documents, giving an IDF of $16.6$ (base 2). A document that mentions transformer five times receives a TF-IDF score of $5 \cdot 7.64 = 38.2$ for that term, whereas mentioning the five times still scores $0$. The function thus elevates rare, content-bearing words while suppressing frequent function words.

What are the common variants of TF and IDF?

The basic recipe admits many variations, and the choice of variant matters for retrieval and classification accuracy. The standard SMART notation, introduced by Salton and refined by Buckley, encodes a TF-IDF scheme as a triplet of letters: the term frequency variant, the document frequency variant, and the normalization.^[2] A document weighting and a query weighting are then written together as ddd.qqq. The following table summarizes the most common choices.

Scroll sideways for more →

For the document frequency factor, the variants are fewer but equally important.

Scroll sideways for more →

Finally, vectors are usually normalized to control for differences in document length, since longer documents otherwise accumulate larger vectors and would dominate cosine similarity comparisons.

Scroll sideways for more →

A classical pairing in IR practice is the SMART code lnc.ltc. Documents use logarithmic TF, no IDF, and cosine normalization (because IDF only matters for the query side in a one-sided weighting scheme). Queries use logarithmic TF, standard IDF, and cosine normalization. This combination is recommended in Manning, Raghavan, and Schutze and is the default setting for many academic IR baselines.^[4]

Vector Space Model and Cosine Similarity

TF-IDF is most often used inside the vector space model of information retrieval, introduced by Salton, Wong, and Yang in 1975.^[3] In this model, both documents and queries are mapped to vectors in a high-dimensional vocabulary space, with each axis corresponding to a unique term. The relevance of a document to a query is computed as the cosine of the angle between the document vector $\vec{d}$ and the query vector $\vec{q}$:

$\text{sim}(\vec{q}, \vec{d}) = \frac{\vec{q} \cdot \vec{d}}{\|\vec{q}\|_2 \cdot \|\vec{d}\|_2}.$

If both vectors are L2-normalized, this reduces to the dot product, which is fast to compute over sparse vectors using inverted indexes. Cosine similarity is invariant to vector scaling, so it focuses on direction (which terms appear together) rather than magnitude (how long the document is). For TF-IDF vectors, the cosine measures the overlap of distinctive vocabulary, weighted by how rare each shared term is in the corpus. This pairing of TF-IDF weights with cosine similarity over an inverted index was the workhorse of search engines from the 1970s through the early 2000s. Apache Lucene, and therefore Solr and Elasticsearch, retained a TF-IDF scoring scheme (its ClassicSimilarity) as the default ranking function until Lucene 6.0 made BM25 the default in 2016.^[15]

How does TF-IDF relate to BM25?

BM25, formally Okapi BM25, is a probabilistic ranking function developed by Stephen Robertson, Karen Sparck Jones, and colleagues at City University London in the 1980s and 1990s.^[7] It is best understood as a refined cousin of TF-IDF that fixes two well known weaknesses of the basic formula. The BM25 score for a document $D$ given a query $Q$ is

$\text{score}(D, Q) = \sum_{t \in Q} \text{idf}(t) \cdot \frac{\text{tf}(t, D) \cdot (k_1 + 1)}{\text{tf}(t, D) + k_1 \cdot (1 - b + b \cdot |D| / \text{avgdl})}$

where $k_1$ controls term frequency saturation (typically $1.2$ to $2.0$), $b$ controls length normalization (typically $0.75$), and $\text{avgdl}$ is the average document length in the corpus.^[15] The IDF term is usually the probabilistic variant $\log((N - \text{df}(t) + 0.5) / (\text{df}(t) + 0.5))$, which can be negative for very common terms and is sometimes clipped to zero.^[6]

The two improvements over TF-IDF are easy to read off the formula. First, term frequency saturates: as $\text{tf}(t, D)$ grows, the contribution of term $t$ approaches an asymptote of $\text{idf}(t) \cdot (k_1 + 1)$, capturing the intuition that the tenth occurrence of transformer in a paper is much less informative than the first. Second, document length is normalized smoothly via the $b$ parameter, so a long document is not penalized as harshly as it would be by raw TF and not entirely free of length penalty either. In benchmarking by Elastic, the search vendor behind Elasticsearch, "BM25 performed far better than the default similarity" on the test collections it evaluated, which is part of why the open source search ecosystem migrated to it.^[16] The following table contrasts the two methods on the dimensions practitioners care about.

Scroll sideways for more →

BM25 is now the default lexical ranking function in nearly every modern open source search engine, and TF-IDF is largely retained as a feature representation for downstream models rather than a standalone ranker.^[15] The two methods are close kin, however, and often produce similar rankings on short queries with rare terms.

Implementation in scikit-learn

In the Python ecosystem, the canonical implementation is sklearn.feature_extraction.text.TfidfVectorizer.^[11] It combines tokenization, vocabulary building, and TF-IDF weighting into a single transformer with sensible defaults. A typical use looks like

from sklearn.feature_extraction.text import TfidfVectorizer

corpus = [
    "The cat sat on the mat",
    "Cats are excellent climbers",
    "Dogs are loyal companions",
]
vectorizer = TfidfVectorizer()
X = vectorizer.fit_transform(corpus)
print(vectorizer.get_feature_names_out())
print(X.toarray())

The vectorizer returns a sparse matrix of shape (n_documents, n_features). Several constructor parameters control the variant in use. The following table covers the most important ones.

Scroll sideways for more →

A few practical notes follow from these defaults. First, scikit-learn's IDF formula differs slightly from the textbook by adding 1 to both numerator and denominator (smoothing) and adding 1 to the result, so a term that appears in every document has IDF $1$ rather than $0$.^[13] Combined with L2 normalization, this means common terms still contribute, just less than rare ones. Second, sublinear_tf=True is recommended for long documents because it dampens the effect of repeated terms much like BM25 does. Third, fitting the vectorizer on the training set and only transforming the test set is essential to avoid leaking test-set vocabulary statistics into the model.

The related TfidfTransformer accepts a precomputed term-count matrix (for instance from CountVectorizer) and applies the IDF and normalization steps.^[13] Splitting these into two stages is convenient when the same counts feed multiple downstream models with different weighting schemes.

What is TF-IDF used for in text classification?

For decades, the standard pipeline for text classification was to convert documents to TF-IDF vectors and feed them into a linear classifier such as a support vector machine, logistic regression, or multinomial naive Bayes. This combination is fast, interpretable, and surprisingly competitive on tasks like topic classification, sentiment analysis, spam detection, and authorship attribution. Thorsten Joachims's 1998 paper Text Categorization with Support Vector Machines established the linear SVM with TF-IDF features as the baseline that any new method had to beat, a status it retained for nearly twenty years until neural networks finally surpassed it on most benchmarks.^[10]

The pairing works for several reasons. TF-IDF vectors are high-dimensional and sparse, a regime in which linear models with appropriate regularization are statistically efficient and computationally cheap.^[10] The feature representation is interpretable: examining the largest positive and negative weights of a logistic regression trained on TF-IDF features tells you which words are most predictive of each class. The model also trains in seconds on millions of documents, which is essential for iterative experimentation. Spam filters in mail systems through the 2000s and 2010s relied heavily on TF-IDF features fed into naive Bayes or SVM classifiers, often updated continuously as new spam patterns appeared. Even today, many production text-classification systems use TF-IDF features as a fast first-stage model, with neural reranking applied only to ambiguous cases.

Use in Keyword Extraction and Summarization

TF-IDF is a natural method for keyword extraction. To find the most distinctive terms in a document, compute the TF-IDF weights of all terms relative to a corpus and return the top-$k$ by weight. This works well when the corpus is large and topically diverse, because the IDF factor automatically downweights vocabulary that is generic across topics. The same idea underlies tag suggestion, search result snippets, and the construction of word clouds. For multi-document summarization, TF-IDF can score sentences by summing the weights of their constituent terms, then select the top-scoring sentences subject to a length budget and a redundancy penalty. This was the basis of the LexRank and TextRank algorithms before transformer-based summarizers became standard. TF-IDF features are also used to seed clustering algorithms like k-means for topic discovery, where each cluster centroid can be interpreted as a synthetic document whose top TF-IDF terms describe the cluster's theme.

Is TF-IDF still relevant? Hybrid Retrieval and Beyond

Dense vector representations from neural models such as BERT, Sentence-BERT, and OpenAI's text embedding models have largely supplanted TF-IDF for tasks that require true semantic search. Dense embeddings can match a query about automobile to a document about cars, recognize paraphrases, and bridge across languages, none of which TF-IDF can do because it treats car and automobile as unrelated atomic tokens. The vector space model has also evolved: instead of millions of sparse axes corresponding to vocabulary, dense models map text to a few hundred dense dimensions that encode latent semantic features. See word embedding for the foundational neural representations of text.

For exact-keyword tasks, however, TF-IDF and its successor BM25 remain dominant. A search for a serial number, error code, drug name, gene symbol, or rare proper noun is best served by a system that knows that the exact spelling matters and that rarity in the corpus is informative, both of which TF-IDF captures naturally. This is why modern retrieval systems increasingly use hybrid retrieval, combining a sparse lexical retriever (TF-IDF or BM25) with a dense neural retriever and fusing the rankings, often via Reciprocal Rank Fusion (RRF). The lexical channel anchors rare or out-of-vocabulary terms that the neural channel may miss, while the neural channel handles synonymy, paraphrase, and contextual nuance. Studies of retrieval-augmented generation systems have repeatedly found that hybrid retrieval outperforms either approach in isolation, especially on heterogeneous corpora and ambiguous queries.

Scroll sideways for more →

In machine learning pipelines that operate on tabular data with text fields, TF-IDF features are often used alongside numeric features in tree-based models like XGBoost or LightGBM. Because TF-IDF features are sparse and interpretable, they fit naturally into feature engineering workflows where the data scientist wants to understand which words drive predictions.

What are the limitations of TF-IDF?

TF-IDF has several well known limitations that motivated the move to dense representations and to BM25. The bag-of-words assumption discards word order and grammatical structure. Sentences like the dog bit the man and the man bit the dog produce identical TF-IDF vectors, even though their meanings are reversed. Negation, modifiers, and compound noun phrases all suffer from this. Adding bigrams or trigrams partially addresses the problem but increases vocabulary size and sparsity. See bag of words for the underlying representation that TF-IDF inherits this property from.

TF-IDF has no notion of semantics. Two documents that discuss the same topic in entirely different vocabularies receive a near-zero similarity score, even though a human reader would recognize them as related. Synonyms, related concepts, hypernyms, and paraphrases are invisible to the algorithm. Latent semantic indexing (LSI), latent Dirichlet allocation (LDA), and modern embeddings were developed in part to solve this problem. Length normalization in basic TF-IDF is crude unless cosine or pivoted normalization is used.^[9] Raw TF-IDF scores grow with document length, so long documents tend to dominate retrieval results. BM25's smoothed length normalization handles this more gracefully.

TF-IDF assumes a fixed corpus. Adding new documents shifts the IDF values of every term, which can be inconvenient in streaming or dynamic settings. Approximate methods like hashed TF-IDF or incremental IDF updates exist but introduce their own trade-offs. Finally, TF-IDF is an unsupervised heuristic. It does not learn from labeled data, so it cannot exploit signal about which terms matter for a downstream task. Supervised feature weighting schemes such as supervised TF-IDF, delta-IDF, and learned sparse retrievers like SPLADE attempt to combine the interpretability and exact-match strengths of TF-IDF with task-specific learning.^[12]

Variants and Extensions

Researchers have proposed many extensions to the basic TF-IDF formula, motivated by specific deficiencies or specific tasks. Delta TF-IDF weights terms by the difference between their IDF in two corpora, capturing the contrast between, say, a positive-sentiment corpus and a negative-sentiment corpus. It is useful for sentiment analysis and other contrastive tasks. Okapi BM25, discussed above, replaces linear TF with a saturating function and adds principled length normalization.^[7] BM25F extends BM25 to weighted document fields, useful when documents have structure (title, body, anchor text) and different fields should receive different weights. TF-PDF (Term Frequency-Proportional Document Frequency) is a variant used in topic detection and tracking, designed for streaming text where IDF is unstable.

Pivoted unique normalization corrects a length bias in cosine-normalized TF-IDF and was shown by Singhal, Buckley, and Mitra (1996) to improve retrieval effectiveness on long documents.^[9] Supervised TF-IDF and gain-weighted TF-IDF replace the IDF factor with a discriminative measure such as information gain, chi-squared statistic, or odds ratio, computed against labeled training data. Hashing TF-IDF (sometimes called feature hashing or the hashing trick) replaces the explicit vocabulary with a fixed-size hash table, trading a small amount of accuracy for the ability to process truly enormous corpora without storing a vocabulary. Learned sparse retrievers like SPLADE and uniCOIL use neural networks to predict sparse vectors with TF-IDF-like structure, combining the inverted index efficiency of TF-IDF with the semantic generalization of neural embeddings.^[12]

When was TF-IDF invented? A timeline

The key milestones in TF-IDF's development span more than half a century. In 1957, Hans Peter Luhn at IBM proposed using term frequency to identify keywords for automatic abstracting, in his paper A Statistical Approach to Mechanized Encoding and Searching of Literary Information.^[5] Luhn observed that the resolving power of significant words is highest at intermediate frequencies, neither very common nor very rare, an early hint of TF-IDF's combined logic.^[5]

In 1972, Karen Sparck Jones, working at the Cambridge Language Research Unit, published A Statistical Interpretation of Term Specificity and Its Application in Retrieval in the Journal of Documentation.^[1] The paper proposed weighting terms by their inverse document frequency and provided empirical evidence that this weighting improved retrieval.^[1] Sparck Jones did not call her quantity IDF in that paper, but the formula and its motivation are exactly what is now meant by IDF. Her work was foundational, and IDF is sometimes called the Sparck Jones weight.

Through the 1970s, Gerard Salton and his collaborators at Cornell developed the SMART information retrieval system, which combined TF and IDF weights with the vector space model and cosine similarity. The 1975 paper by Salton, Wong, and Yang, A Vector Space Model for Automatic Indexing, formalized the framework that is still taught in IR courses today.^[3] In 1988, Salton and Buckley published Term-weighting approaches in automatic text retrieval in Information Processing and Management. Drawing on years of experiments with the SMART system, the paper catalogued the variants of TF and IDF, introduced the SMART notation, and argued for specific combinations as best practice.^[2] It remains one of the most cited papers in information retrieval and is the source for many of the variant formulas listed above.

The Robertson and Sparck Jones probabilistic relevance model, developed through the 1970s and 1980s, generalized IDF into the probabilistic framework that eventually produced BM25.^[6] Stephen Robertson and Steve Walker's 1994 TREC papers introduced the BM25 formula explicitly, and by the 2000s BM25 had become the de facto improvement over basic TF-IDF.^[7] In the late 2000s and 2010s, the rise of word embeddings (word2vec in 2013, GloVe in 2014) and contextual embeddings (ELMo in 2018, BERT in 2018) shifted research attention from sparse weighted vectors to dense neural representations. In 2016, Apache Lucene 6.0 replaced its long-standing TF-IDF ClassicSimilarity with BM25 as the default scoring function, and Elasticsearch 5.0 inherited the change, marking the moment BM25 displaced TF-IDF as the default ranker across most production search.^[16] By the early 2020s, the dominant approach to semantic retrieval was dense vector search using transformer-based encoders. TF-IDF and BM25 receded to the role of strong baselines and as components of hybrid retrieval systems.

TF-IDF in Practice Today

Despite the dominance of dense embeddings in research, TF-IDF remains ubiquitous in production. The reasons are practical. TF-IDF is fast, deterministic, and requires no training data or GPU. Its memory footprint is small enough that a vocabulary of millions of terms fits comfortably in RAM, and inverted indexes deliver sub-millisecond query latency on modern hardware. Its scores are interpretable, which is essential in regulated industries like healthcare, law, and finance, where ranking decisions may need to be explained to auditors. It also works out of the box on any corpus in any language without fine-tuning.

A non-exhaustive list of present-day TF-IDF use cases includes the following. Internal enterprise search systems often use TF-IDF or BM25 as the primary ranker, sometimes with a neural reranker on the top results. Log search engines like Splunk and Elastic are dominated by lexical scoring because exact matches on error messages and identifiers are paramount. Code search inside IDEs frequently relies on TF-IDF over symbol names because semantic models struggle with rare identifiers and short queries. Document deduplication uses TF-IDF cosine similarity as a fast first-stage filter before more expensive comparisons. Plagiarism detection compares TF-IDF vectors to find suspiciously similar passages. Tag and category suggestion in CMS systems pulls top TF-IDF terms as suggested tags. Spam and content moderation pipelines use TF-IDF features inside lightweight linear classifiers as the first line of defense. The text fields of tabular data in Kaggle competitions are routinely converted to TF-IDF vectors and concatenated with numeric features for tree-based models. Educational software uses TF-IDF for short-answer scoring and for matching student responses to model answers.

For a working machine learning practitioner in 2026, the right mental model is straightforward. TF-IDF is a strong, simple, interpretable baseline that should always be tried first. If it solves the problem, the additional cost and complexity of a neural model may not be justified. If it does not, dense embeddings or a hybrid system are the next step. Even when a neural system is the final choice, TF-IDF often makes sense as a feature, a fast pre-filter, or a debugging tool for understanding why the neural model produces particular results.

See Also

• BM25
• Information Retrieval
• Bag of Words
• Word Embedding
• Natural Language Processing
• Retrieval-Augmented Generation
• Semantic Search
• Support Vector Machine

References

1. Sparck Jones, K. (1972). A statistical interpretation of term specificity and its application in retrieval. *Journal of Documentation*, 28(1), 11-21. staff.city.ac.uk/~sbrp622/idfpapers/ksj_orig.pdf ↩
2. Salton, G., & Buckley, C. (1988). Term-weighting approaches in automatic text retrieval. *Information Processing & Management*, 24(5), 513-523. ↩
3. Salton, G., Wong, A., & Yang, C. S. (1975). A vector space model for automatic indexing. *Communications of the ACM*, 18(11), 613-620. ↩
4. Manning, C. D., Raghavan, P., & Schutze, H. (2008). *Introduction to Information Retrieval*. Cambridge University Press. ISBN 978-0-521-86571-5. nlp.stanford.edu/IR-book ↩
5. Luhn, H. P. (1957). A statistical approach to mechanized encoding and searching of literary information. *IBM Journal of Research and Development*, 1(4), 309-317. ↩
6. Robertson, S. E., & Sparck Jones, K. (1976). Relevance weighting of search terms. *Journal of the American Society for Information Science*, 27(3), 129-146. ↩
7. Robertson, S. E., Walker, S., Jones, S., Hancock-Beaulieu, M. M., & Gatford, M. (1995). Okapi at TREC-3. *Proceedings of the Third Text REtrieval Conference (TREC-3)*, 109-126. ↩
8. Robertson, S. (2004). Understanding inverse document frequency: on theoretical arguments for IDF. *Journal of Documentation*, 60(5), 503-520. ↩
9. Singhal, A., Buckley, C., & Mitra, M. (1996). Pivoted document length normalization. *Proceedings of the 19th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval*, 21-29. ↩
10. Joachims, T. (1998). Text categorization with support vector machines: Learning with many relevant features. *Proceedings of the 10th European Conference on Machine Learning (ECML)*, 137-142. ↩
11. Pedregosa, F., Varoquaux, G., Gramfort, A., Michel, V., Thirion, B., Grisel, O., Blondel, M., Prettenhofer, P., Weiss, R., Dubourg, V., Vanderplas, J., Passos, A., Cournapeau, D., Brucher, M., Perrot, M., & Duchesnay, E. (2011). Scikit-learn: Machine learning in Python. *Journal of Machine Learning Research*, 12, 2825-2830. ↩
12. Formal, T., Lassance, C., Piwowarski, B., & Clinchant, S. (2021). SPLADE v2: Sparse lexical and expansion model for information retrieval. arXiv:2109.10086. ↩
13. scikit-learn developers. *TfidfVectorizer documentation*. scikit-learn.org/stable/modules/generated/sklearn.feature_extraction.text.TfidfVectorizer.html ↩
14. Wikipedia contributors. *tf-idf*. en.wikipedia.org/wiki/Tf-idf ↩
15. Wikipedia contributors. *Okapi BM25*. en.wikipedia.org/wiki/Okapi_BM25 ↩
16. Elastic. *BM25 vs Lucene Default Similarity*. Elastic Blog. elastic.co/blog/found-bm-vs-lucene-default-similarity ↩