Visualizing keyword importance through frequency-based spatial distribution.
Input Text
Parameters
40
Cloud View
Active
Statistics
Total Words0
Unique Vocab0
Filtered0
Insight
Size represents term frequency ($tf$). Larger words appear more often in your source text.
Low Freq
High Freq
Overview
What the picture encodes
Font size maps to frequency: the most common word is largest, and all of it else is scaled relative to it. Position, colour and rotation almost always carry no data. They are chosen by a layout algorithm packing shapes into a space without overlap.
That is the first thing to know about reading one. Two words next to each other are not related; they simply fitted. Any interpretation based on adjacency or colour is reading structure that was never encoded.
A word cloud is, at its core, a frequency bar chart with the axes removed and the bars replaced by the words themselves. That makes it visually engaging and easy to scan, which is why it shows up in presentations and dashboards. But it also means it inherits every limitation of a frequency count. Words with similar counts are drawn at similar sizes, and the human eye is poor at comparing font sizes. So the ranking among mid-frequency words is unreliable. A bar chart would show those differences exactly; a word cloud hides them.
The preparation step matters more than the layout. Raw text fed into a word cloud generator will produce a cloud dominated by "the", "is", "and" and other stopwords that tell you nothing about the content. Removing stopwords, lowercasing, and optionally stemming or lemmatising the words is what turns the cloud from a picture of English grammar into a picture of the document's subject matter.
Word clouds work best as a first-pass exploration tool: glance at the biggest words, form a hypothesis about what the corpus contains. Then verify with actual counts or a more precise visualisation. Treating them as evidence rather than as a prompt for further investigation is the mistake that leads to misleading conclusions. A topic mentioned in every document with moderate frequency will be large. While a topic mentioned heavily in one document and nowhere else may not appear at all, depending on the aggregation.
Visualizing keyword importance through frequency-based spatial distribution.
A word cloud sizes each word by how often it appears. It is genuinely useful for a first look at a corpus, and it is a frequency chart with the axes removed - which is worth knowing before drawing conclusions from one.
What the picture encodes
Font size maps to frequency: the most common word is largest, and all of it else is scaled relative to it. Position, colour and rotation almost always carry no data. They are chosen by a layout algorithm packing shapes into a space without overlap.
That is the first thing to know about reading one. Two words next to each other are not related; they simply fitted. Any interpretation based on adjacency or colour is reading structure that was never encoded.
A word cloud is, at its core, a frequency bar chart with the axes removed and the bars replaced by the words themselves. That makes it visually engaging and easy to scan, which is why it shows up in presentations and dashboards. But it also means it inherits every limitation of a frequency count. Words with similar counts are drawn at similar sizes, and the human eye is poor at comparing font sizes. So the ranking among mid-frequency words is unreliable. A bar chart would show those differences exactly; a word cloud hides them.
The preparation step matters more than the layout. Raw text fed into a word cloud generator will produce a cloud dominated by "the", "is", "and" and other stopwords that tell you nothing about the content. Removing stopwords, lowercasing, and optionally stemming or lemmatising the words is what turns the cloud from a picture of English grammar into a picture of the document's subject matter.
Word clouds work best as a first-pass exploration tool: glance at the biggest words, form a hypothesis about what the corpus contains. Then verify with actual counts or a more precise visualisation. Treating them as evidence rather than as a prompt for further investigation is the mistake that leads to misleading conclusions. A topic mentioned in every document with moderate frequency will be large. While a topic mentioned heavily in one document and nowhere else may not appear at all, depending on the aggregation.
Why stopwords have to go
Run a word cloud on raw English text and you get the, of, and, to, a in enormous type. These are the most frequent words in almost any corpus and they tell you nothing about the subject.
Removing them is what makes the visualisation informative, and it is a genuine editorial choice rather than a technical detail. Standard stopword lists are a reasonable default; domain-specific ones usually matter more. In a corpus of medical papers, patient and study may be so ubiquitous that they crowd out all of it that distinguishes one paper from another.
A frequency chart that happens to look like art
A word cloud draws each word at a size proportional to how often it appears. That is the whole visualisation: size encodes frequency, and all of it else — colour, rotation, position — is decoration.
Which is worth stating plainly, because it sets both the use and the limits. It answers "what words dominate this text?" quickly and legibly. And it answers nothing else.
The pipeline behind one:
Tokenise the text into words.
Normalise — lowercase, strip punctuation.
Remove stop words, or "the" and "and" will dominate every cloud ever made.
Count the remaining words.
Lay out the top n by size, fitting them into the available space.
Step 3 is what makes the difference between a useful cloud and a picture of English function words.
from wordcloud import WordCloud
from sklearn.feature_extraction.text import ENGLISH_STOP_WORDS
wc = WordCloud(width=1200, height=600, background_color="white",
stopwords=set(ENGLISH_STOP_WORDS),
max_words=100, collocations=False).generate(text)
wc.to_file("cloud.png")
collocations=False is worth knowing: by default the library includes two-word phrases. This is sometimes desirable and often produces duplicated content ("machine", "learning" and "machine learning" all present).
Why counts alone mislead
Raw frequency has a systematic bias: it favours words that are common in the language, not words that are distinctive to this text.
Remove stop words and the next tier takes over — "said", "one", "time", "people". A cloud of a thousand product reviews will prominently feature "product". This tells you nothing you did not already know.
TF-IDF weighting fixes this by dividing by how many documents contain each word. So terms appearing everywhere are suppressed and terms distinctive to this document are amplified:
generate_from_frequencies is the function to know: it takes any dictionary of word-to-weight. So the sizes can encode TF-IDF, log-odds against a comparison corpus, or a sentiment score. Anything more informative than a raw count.
The honest limitations
Word clouds are widely criticised in data visualisation, and the criticisms are correct:
Area is hard to compare. People judge length well and area poorly. So a word twice as frequent does not look twice as prominent. A bar chart of the top 20 terms conveys the same data far more exactly.
Long words look more important. "Implementation" occupies more space than "cost" at the same font size. So word length confounds the encoding.
Position is meaningless but reads as meaningful. Words near the centre appear more important, and the layout algorithm placed them there for packing reasons.
No context or relationships. "Not good" appears as "good". Negation, phrases and sentiment are all invisible.
Rotation hurts legibility for no informational gain.
So the fair summary: a word cloud is a reasonable first look at an unfamiliar corpus and a poor analytical tool. Use it to orient yourself, then use a bar chart, a keyness comparison or a topic model to say anything specific.
Interactive Exploration Guide
Turn the filter off. Disable Stopwords Filter and press Generate. The cloud fills with function words and says nothing about the content. Raw frequency is dominated by grammar, not meaning.
Turn it back on. Enable the filter and regenerate. Content words emerge, and the picture becomes about the subject matter.
Restrict the vocabulary. Set Max Words to 10 and generate. Only the strongest signals survive. Now raise it to 100 — the long tail of near-equal words adds visual noise without adding data.
Regenerate without changing anything. Press Generate twice at the same settings. The layout shifts while the sizes stay the same, which shows directly that position carries no meaning.
Where raw frequency misleads, and what to use instead
Frequency alone conflates “important in this document” with “common broadly”. The standard correction is TF-IDF, which weights a word by how often it appears in this document and divides by how many documents contain it at all:
tf-idf = tf(word, doc) × log(N / df(word))
A word appearing in every document gets an IDF near zero and drops out; a word frequent here and rare elsewhere scores highly. That is much closer to what people actually want a word cloud to show. What is distinctive about this text, not merely what is in it.
The other limitation is that area is a poor visual encoding. People judge length far more accurately than area, so a bar chart conveys the same data more exactly. The word cloud’s advantage is that it is quick to scan and shows many terms at once. Useful for exploration, weak for comparison.
What usually goes wrong
Skipping normalisation. Without lowercasing and lemmatising, Run, run, running and ran are four separate entries splitting one word’s weight.
Comparing two clouds. Each is scaled to its own maximum. So a word the same size in two clouds may have very different counts. Comparison needs a shared scale, which means a chart.
Reading meaning into layout. Position and colour are decoration. Adjacency implies nothing.
Using raw counts on documents of different lengths. A longer document has larger counts throughout; normalise by length or use TF-IDF.
Key takeaway
A word cloud encodes frequency as font size and nothing else. Position, colour and rotation are layout, not data. It needs stopword removal to say anything at all, and TF-IDF rather than raw frequency to show what is distinctive rather than merely common. Treat it as a fast exploratory glance at a corpus, and reach for a bar chart when the question is how much bigger one term is than another.
Better options, by question
Question
Better tool
Which terms are most frequent?
A horizontal bar chart of the top 20
Which terms distinguish A from B?
Keyness or log-odds ratio, plotted
What topics are present?
LDA or BERTopic, with top terms per topic
How does usage change over time?
A line chart of term frequency by period
Which terms co-occur?
A co-occurrence network graph
What is the sentiment?
A sentiment model, not word counts
The second row deserves emphasis because it is the question people usually mean. Comparing two corpora — positive versus negative reviews, this year versus last — and plotting the terms with the largest difference in relative frequency is far more informative than two word clouds side by side. And it is a standard technique in corpus linguistics.
BERTopic is worth knowing as the modern option: embed the documents, cluster the embeddings, and extract distinguishing terms per cluster. It finds themes rather than words, and it handles the "not good" problem because embeddings are contextual.
When a word cloud is the right choice
Not never — there are cases where it truly fits:
Exploratory orientation. First contact with an unfamiliar corpus, to see what register and subject matter you are dealing with.
Presentation to a non-technical audience, where an at once legible impression matters more than precision. It communicates "here is what this text is about" in one glance.
A visual element in a report or dashboard where the analytical content is carried by other charts.
What to do to make it as good as it can be: remove stop words aggressively, weight by TF-IDF rather than count, disable rotation, cap at 50–100 words, use a single colour or a colour that encodes something real, and put a bar chart of the top terms next to it.
Practical gotchas
Stop words are language-specific. An English list applied to French text leaves "le", "de" and "et" dominating.
Domain stop words matter too. In product reviews, "product", "item" and the brand name are noise; add them to the list.
Lemmatise or accept duplicates. "Run", "runs" and "running" appear as three words if not.
Watch for a dominating single term that compresses all of it else to illegibility. A log scale on the weights helps.
Numbers and URLs usually want removing.
Font support. Non-Latin scripts need a font that contains them. Or the cloud renders as boxes.
What a word cloud shows, and what it hides
A word cloud is a frequency count with a font size attached. Building one from raw counts and then from TF-IDF shows why the raw version almost always says the same thing no matter the text.
example_01.pyNumPy
from collections import Counter
import re
text = ("The quarterly report shows that revenue growth in the cloud division "
"exceeded expectations. The cloud business grew 34 percent while the "
"hardware division declined. Analysts noted that the cloud margin "
"improved and that the company expects cloud revenue to continue "
"growing. The report also noted that hardware revenue fell for the "
"third quarter in a row and that the company is shifting investment "
"toward the cloud.")
words = re.findall(r"[a-z]+", text.lower())
counts = Counter(words)
print("%d words, %d distinct." % (len(words), len(counts)))
print()
print("RAW COUNTS -- what a naive word cloud would size by:")
for w, c in counts.most_common(10):
print(" %-14s %3d %s" % (w, c, "#" * (c * 3)))
print()
print("the top of that list is 'the', 'that' and 'in'. a word cloud built")
print("from raw counts is mostly a picture of English, not of this document.")
print()
STOP = set(("the a an and or but in on at to for of that this is are was were "
"it its as with by from has have had will would can could").split())
filtered = Counter({w: c for w, c in counts.items() if w not in STOP and len(w) > 2})
print("AFTER STOPWORD REMOVAL, which is the minimum any tool does:")
for w, c in filtered.most_common(10):
print(" %-14s %3d %s" % (w, c, "#" * (c * 3)))
print()
print("better -- 'cloud' and 'revenue' are genuinely what this text is")
print("about. but the stopword list is doing the work, and it is a fixed")
print("list somebody else wrote.")
print()
Output
Building on the same setup, the next block shows the remaining cases.
example_02.pyNumPy
from collections import Counter
import re
reference = Counter(("the company reported results for the quarter revenue "
"was in line with expectations the division performed "
"and the report noted results the company said that "
"growth in the business was steady the quarter results "
"report company revenue division business growth").split())
import math
N_REF = sum(reference.values())
N_DOC = sum(filtered.values())
print("TF-IDF STYLE -- score each word against how common it is in a")
print("reference corpus of similar documents, rather than against a list:")
print("%14s %10s %14s %12s" % ("word", "in doc", "in reference", "score"))
scored = []
for w, c in filtered.items():
ref = reference.get(w, 0)
score = (c / N_DOC) * math.log((N_REF + 1) / (ref + 1))
scored.append((score, w, c, ref))
for score, w, c, ref in sorted(scored, reverse=True)[:10]:
print("%14s %10d %14d %12.4f" % (w, c, ref, score))
print()
print("now the ranking is about what makes THIS document unusual. 'revenue'")
print("and 'company' appear here and in every other quarterly report, so")
print("they fall. 'cloud' stays at the top because it does not.")
print()
print("THE THREE THINGS A WORD CLOUD CANNOT SHOW:")
print()
print(" 1. ORDER. these two sentences produce the SAME bag of words:")
pair = ("the cloud division grew and hardware declined",
"hardware grew and the cloud division declined")
bags = []
for sent in pair:
ws = sorted(w for w in re.findall(r"[a-z]+", sent.lower()) if w not in STOP)
Output
The following block covers the remaining operations.
example_03.pyNumPy
bags.append(ws)
print(" %s" % sent)
print(" -> %s" % " ".join(ws))
print(" identical: %s" % (bags[0] == bags[1]))
print(" those two sentences say opposite things about the business, and")
print(" a word cloud draws them the same way.")
print()
print(" NEGATION is the same problem wearing a different hat: 'not' is")
print(" on almost every stopword list, so 'margins improved' and")
print(" 'margins did not improve' can land in the same picture.")
print()
print(" 2. RELATIONSHIPS. 'cloud' appears %d times and 'revenue' %d times."
% (counts["cloud"], counts["revenue"]))
print(" whether they appear TOGETHER is invisible. a bigram count says:")
bigrams = Counter(zip(words, words[1:]))
with_cloud = [(p, c) for p, c in bigrams.items() if "cloud" in p]
print(" every pair containing 'cloud':")
for p, c in sorted(with_cloud, key=lambda kv: -kv[1]):
print(" %-24s %d" % (" ".join(p), c))
together = sum(c for p, c in with_cloud if "revenue" in p)
print(" 'cloud' and 'revenue' appear adjacent %d time(s). the cloud"
% together)
print(" shows you both words are frequent and never that they are")
print(" related -- and 'cloud division', 'cloud business' and 'cloud")
print(" margin' are three distinct facts it collapses into one word.")
print()
print(" 3. SCALE. font size maps to count, and human area perception is")
print(" not linear. a word twice as frequent drawn at twice the height")
print(" covers four times the area:")
for c in (2, 4, 8, 16):
print(" count %2d -> height %2dx -> area %3dx" % (c, c // 2, (c // 2) ** 2)
if c >= 2 else "")
print(" so the picture systematically exaggerates the top few words.")
print()
print("word clouds are a reasonable first look at an unfamiliar corpus and a")
print("poor basis for a claim. if the finding matters, report the counts.")
Output
Questions people ask
Are word clouds bad? They are imprecise, which is a real limitation for analysis and not disqualifying for orientation and presentation.
Should I remove stop words? Always, or the cloud shows the structure of the language rather than the content of the text.
Can I use TF-IDF instead of counts? Yes, via generate_from_frequencies, and it usually produces a much more informative cloud.
Does colour mean anything? By default no. You can map it to something real — sentiment, topic, part of speech — and then it does.
How many words should I show? 50–100. Beyond that the small words are unreadable and add nothing.
What about phrases? Bigrams can be included, and watch for the duplication that produces ("machine", "learning", "machine learning").
Recap in one screen
A word cloud encodes frequency as font size; all of it else is decoration.
Remove stop words, or every cloud shows the same function words.
Weight by TF-IDF rather than raw count to surface what is distinctive rather than what is common.
Area comparison is imprecise and word length confounds it. A bar chart says the same thing more accurately.
Good for orientation and presentation; use keyness comparison or topic modelling for analysis.
Recall check
0 of 4
Say the answer out loud before you reveal it — recalling it is what makes it stick, and rereading it is not.
What is meant by “Stop words are language-specific” here?
What is meant by “Domain stop words matter too” here?
What is meant by “Lemmatise or accept duplicates” here?
What is meant by “Watch for a dominating single term” here?
Cheat sheet
Word Cloud Generator
Paste any text and watch a word cloud size each term by how often it appears, exposing what a document is really about.
Ashish Jangra builds and maintains VizLearn. Every module here is written and the visualisation behind it hand-built, so the numbers in a readout come from the same code that draws the picture. Corrections are genuinely welcome and get priority over everything else — if a page states something wrong, or an animation misrepresents what the algorithm does, get in touch.