Reading an inequality from a number line comes down to two visual features: the circle style at the endpoint tells you whether the boundary value is included, and the arrow's direction tells you which side of that boundary the solution lies on. A closed, filled circle pairs with ≤ or ≥; an open, hollow circle pairs with < or >. The arrow points the same way the inequality symbol "opens." Get both right and the symbol writes itself.
That is the whole skill in miniature. What trips people up is the second half of the job — confirming the reading by testing an actual value from the shaded region — and the handful of cases where a number line carries two endpoints, no shading between them, or a scale that isn't marked in units of one. The sections below walk through the circle vocabulary, the arrow rule, a five-step reading routine, the bounded "between" case, and the common misreads that survive even after someone knows the basics.
What the hollow and filled circles mean at the endpoint
The endpoint is where the reading starts. In U.S. classrooms the convention is consistent: a hollow circle means the value under it is not part of the solution set, and a filled or closed circle means it is. That single distinction maps directly onto the strict symbols < and > versus the inclusive symbols ≤ and ≥.
Textbook publishers state this explicitly. McGraw-Hill's Algebra 1 graphing chapter, for example, pairs an open dot with "less than" or "greater than" and a closed dot with "less than or equal to" or "greater than or equal to," which is the same convention you'll find in Houghton Mifflin Harcourt's Into Algebra series. If you learned the rule as "open = exclude, closed = include," you learned the version that transfers across almost every U.S. curriculum.
A hollow circle is sometimes drawn as a ring with visible white space inside it; a filled circle is a solid dot. On a printed worksheet scanned at low resolution, a filled dot can smear into something that looks hollow, so check the surrounding shading before you commit. If the line is shaded right up to the dot, treat it as closed even if the dot looks ambiguous.
One more endpoint detail matters: a circle with nothing else on the line is not a graph of anything. An inequality needs both the circle and the ray. If you see a lone dot, you're looking at a point plotted on a number line, not an inequality, and writing x = 3 (or x ≤ 3, if shading follows) depends entirely on what else is drawn.
Match the arrow to the symbol: the direction rule that always works
The arrow tells you the direction of the solution, and the inequality symbol's open end always faces the same way as the arrow. Draw x > 2: the arrow runs right, and the ">" opens toward the right. Draw x < 2: the arrow runs left, and "<" opens toward the left. That visual correspondence is why the mnemonic "the alligator eats the bigger side" persists — the open jaw points at the larger set of values.
There is a cleaner way to phrase it that survives negative numbers. The symbol points from the variable toward the direction of the ray. If the ray goes left, the symbol opening must face left, which gives you "<" when the variable sits on the left: x < 2. If someone writes 2 > x, the symbol opens left toward 2, and the arrow also points left from 2 — same graph, different arrangement. Both are correct, which is why "read the graph" and "read the inequality" are not quite the same task.
Khan Academy's Algebra 1 unit on inequalities leans on exactly this arrow-symbol alignment, and it holds for decimals and fractions as well as integers. The arrow on x ≥ −1.5 runs right from a filled dot at −1.5; the symbol opens right. Nothing about the decimal changes the rule.
Where the rule earns its keep is in negative territory. Students who rely on "greater means to the right" sometimes flip the symbol when the boundary is negative and the arrow still runs right. It doesn't flip. −2 > −5 because −2 sits to the right of −5, and an arrow running right from −5 with a hollow circle reads x > −5, full stop.
A five-step routine for turning any graph into a symbol
Reading a single-ended graph is a short sequence, and running it in the same order every time cuts error rates. The steps below are ordered by what to inspect first, because the circle resolves inclusion before direction matters.
1: Locate the endpoint circle and note its value from the axis labels. 2: Classify the circle as hollow (strict, < or >) or filled (inclusive, ≤ or ≥). 3: Note which way the shaded ray points, left or right. 4: Write the variable, the matching symbol, and the endpoint value, with the symbol opening toward the arrow. 5: Test one plain value from the shaded region in your finished inequality and confirm it makes the statement true.
Step 5 is the one most people skip, and it's the one that catches a flipped sign. If your reading is x < −3 but the shaded region contains −4, substituting gives −4 < −3, which is true, so the reading holds. If you'd written x > −3, substituting −4 gives −4 > −3, which is false, and you know to flip.
Failure handling for step 1: if the endpoint sits between two labeled tick marks, count the subdivisions. A number line labeled at −2 and 0 with one tick between them is marked in units of 1, so the middle tick is −1. If there are four ticks between the labels, each step is 0.4, and the endpoint could be −1.2. Confirm the scale on the assignment's axis legend before writing a decimal, because a misread scale produces a symbol that is right in shape and wrong in value.
The test step also flags the case where the variable is written on the right, as in 5 ≥ x. Rewriting it as x ≤ 5 before testing keeps the substitution honest.
Reading compound inequalities: two circles, one shaded middle
A number line with two endpoints and a shaded segment between them graphs a compound inequality of the "and" type, and it reads as a bounded interval. The left circle supplies the lower bound, the right circle the upper bound, and the shading between them means the solution satisfies both conditions at once. The standard written form puts the variable in the middle: −1 < x ≤ 4, for instance, which describes a hollow circle at −1, a filled circle at 4, and shading between.
The circle types can differ, and they often do on tests. If the left endpoint at −1 is hollow and the right endpoint at 4 is filled, the reading is −1 < x ≤ 4: −1 excluded, 4 included. If both are hollow, it's −1 < x < 4. If both are filled, it's −1 ≤ x ≤ 4. Read each circle independently before you assemble the chain, because the common mistake is assuming both endpoints share a type.
OpenStax's Elementary Algebra section on compound inequalities presents the same convention and adds the detail worth knowing: a bounded interval can also be written with two separate inequalities joined by "and," as x > −1 and x ≤ 4. Both notations describe the identical graph. Some teachers require the chained form; some accept either.
The awkward case is two rays pointing away from each other with a gap between the circles — that's an "or" compound inequality, such as x < −1 or x > 4. No values between −1 and 4 satisfy it. If the graph has two circles and the shading runs outward in both directions rather than between them, don't force it into a chained form; chained notation can't express it. Write the two inequalities joined by "or."
How to read a number line backward to check your own answer
Once you can read a graph, you can also use the skill in reverse: take a written inequality, graph it mentally, and confirm the picture matches what the problem asked for. That check is faster than re-deriving an answer from scratch, and it catches the specific error of flipping the inequality while solving.
Suppose you solved 3x + 1 > 10 and got x > 3. Sketch it: hollow circle at 3, arrow running right, symbol opening right. Then test a value from the shaded side, say 4. Three times 4 plus 1 is 13, and 13 > 10, so the original statement holds. If you had flipped the result to x < 3, the test value 0 would give 1 > 10, which fails immediately.
That reverse-check compresses into one arithmetic motion, and it scales to multi-step problems. For −2x ≥ 6, dividing by a negative flips the symbol to x ≤ −3, which graphs as a filled circle at −3 with the ray running left. Test −4: −2(−4) = 8, and 8 ≥ 6, so the reading is consistent. Flip it by mistake to x ≥ −3 and the test value −4 gives 8 ≥ 6 in the original but −4 ≥ −3 in the graph reading — false. The check exposes the flip.
Run the check whenever a problem involves multiplying or dividing by a negative number, because that's the operation the standard rules require you to flip the symbol for. The reverse-check costs one substitution and saves a whole re-solve.
The number line scale trap that changes the value but not the symbol
Scale is the quiet failure point. A ray with a hollow circle drawn at a tick between 0 and 2 looks identical to one at 1, but the value depends entirely on how the axis is marked. If the axis has only the labels 0, 5, 10 and four unlabeled ticks between each pair, each tick is worth 1, so the second tick after 0 is 2. If the axis is labeled only at 0 and 10 with one tick between them, the middle tick is 5, and an endpoint there reads x < 5, not x < 1.
The trap sharpens with decimals. A graph scaled in hundredths can put an endpoint at 0.75 on a tick one-quarter of the way between 0.5 and 1.5, and a reader who assumes unit spacing writes 1 instead of 0.75. The symbol will be correct and the number wrong, which is the kind of error that survives a quick visual check.
Determine the scale before reading any value. Count the intervals between two labeled marks, divide the difference by the interval count, and you have the value per tick. That's arithmetic anyone can do in their head, and it converts an ambiguous picture into a definite reading.
For horizons where the axis is labeled in a nonstandard step — every 25 on a temperature axis, say — the same division applies, and the resulting endpoint may be a negative value between two labels, such as −12.5. Confirm the scale on the assignment's axis legend when it's given; when it isn't, state your assumption so the reader can follow.
Common misreads, and the mirror-image error that survives them
Four misreads account for most wrong answers on number-line inequality problems, and each has a one-line antidote.
Flipping the arrow and the circle. A hollow circle with a leftward arrow reads x < 3 only if the circle sits at 3. If the circle is at −3 with a leftward arrow, it reads x < −3. The arrow's direction is independent of the sign of the endpoint. Assuming "greater" always means right. It does — but only when the variable is on the left. In 3 < x, the symbol opens away from 3 toward larger values, and the graph runs right from a hollow circle at 3. Rewrite it as x > 3 and the confusion disappears. Reading a bounded segment as two separate rays. Two circles with a shaded middle is a single "between" statement, not two answers. The chained form handles it in one inequality. Treating a lone circle as a full graph. No arrow and no shading means no inequality. Check for shading before writing a symbol.
The mirror-image error that survives all four is this: writing the correct circle type but attaching it to the wrong symbol because you forgot which strict/inclusive pair goes with which circle. Hollow = strict (<, >); filled = inclusive (≤, ≥). Say that pair out loud once during a test and the error drops away.
A fifth case worth flagging is the arrow that terminates at another circle rather than running off the edge. That's still a bounded interval, not a ray, even though the arrow looks like a ray. The two circles are the bounds.
Comparing one-ended and two-ended readings side by side
The fastest way to lock in the difference between ray graphs and segment graphs is a single comparison, arranged so the deciding feature sits in the same column. Look at the boundary count first, then the circle types, then the written form.
| Graph shape | Number of circles | Shading location | Written form | Notes |
|---|---|---|---|---|
| Ray pointing left | 1 | Left of the circle | x < a or x ≤ a | Circle type sets strict vs. inclusive |
| Ray pointing right | 1 | Right of the circle | x > a or x ≥ a | Arrow direction and symbol opening match |
| Segment between two circles | 2 | Between the circles | a < x < b (or mixed ≤) | Read each circle separately |
| Two outward rays | 2 | Outside both circles | x < a or x > b | Chained notation cannot express this |
| Lone circle, no shading | 1 | None | No inequality | A plotted point, not a graph |
The advantage of reading the table rather than memorizing prose is that the segment row forces you to treat the two endpoints as separate decisions. Most segment errors come from assuming both circles match; the table breaks that assumption.
Use the table as a checklist against a homework set. Sort each problem into one of the five rows, and the symbol template follows immediately. A problem that won't sort into any row is usually a misdrawn graph or a single plotted point.
When the variable sits on the right, reverse the reading before you write
Writing an inequality with the variable on the right is legal and common in textbooks, but it inverts the natural reading direction and produces a predictable error. If the graph shows a filled circle at 5 with an arrow running left, and the provided answer choices include both x ≤ 5 and 5 ≥ x, both are correct graphs of the same inequality — the symbol 5 ≥ x opens left toward 5 and the variable sits to the right of the symbol.
The safe move is to rewrite before reading. Take the written form you derived and flip it: 5 ≥ x becomes x ≤ 5, with the symbol flipped and the variable brought to the left. The flipped inequality is easier to test against the shaded region because the substitution reads left to right.
The rule for flipping is fixed: swapping sides reverses the symbol's direction while preserving its strictness. < becomes >, ≤ becomes ≥, and vice versa. OpenStax's algebra texts present this as the symmetry property of inequalities, and it's the same operation used when solving inequalities by multiplying or dividing by a negative number.
If a problem statement insists on the variable on the right, still run the test-value check in the rewritten form, then convert back. That way the arithmetic happens in the form you can verify and only the presentation changes.
The checking habit that makes the reading reliable
Every reading on this page is verifiable by substituting one number from the shaded region. That substitution is the whole reliability system: if the value makes the inequality true, the reading is almost certainly correct; if it fails, one of the two visual features was misread. Do it every time.
The habit pays off beyond number lines. Students who test a value after graphing an inequality are practicing the same move that later verifies solutions to equations and systems. It also builds confidence, which matters on timed tests where the visual judgment has to happen fast.
One cost worth noting: if the shaded region contains no simple integer — a segment from −0.2 to 0.4, for instance — the test value might be 0, which sits in the middle. Test a value that is plainly on one side, like 0.3, and confirm the arithmetic.
None of this replaces a teacher's instruction or the specific conventions of a course. Where a worksheet states a convention — for example, rounding endpoints to the nearest half unit or labeling only integer ticks — follow the worksheet.
FAQ
Does a closed circle always mean the endpoint is included?
Yes, a closed or filled circle includes the endpoint in every U.S. convention I can verify, and it pairs with ≤ or ≥. The exception is a closed circle used to mark a plotted point rather than a ray endpoint, in which case no inequality is being graphed. Check for the shaded ray before writing a symbol.
What does a number line with two arrows pointing outward represent?
It represents an "or" compound inequality such as x < −1 or x > 4, where the shaded regions are the two outer rays and the middle is excluded. Chained "between" notation cannot express it, so the answer is written as two inequalities joined by "or." Testing −2 confirms the left ray; testing 5 confirms the right.
Can a number line show an inequality with no circle at all?
No, a graph of an inequality always includes a circle at its boundary and a shaded ray or segment. A number line with only a shaded region and no visible circle usually has a circle hidden at the edge of the printed frame, so check the axis limits. A shading without a boundary is not a well-formed inequality graph.
How do I read an inequality when the axis is labeled every 10 units?
Divide the distance between two labels by the number of ticks between them to get the per-tick value, then count from the nearest label to the circle. An axis labeled 0 and 10 with four interior ticks marks each tick at 2, so a circle on the third tick reads 6. State the scale you used so the answer is traceable.
Is x > 3 the same graph as 3 < x?
Yes, both describe a hollow circle at 3 with shading to the right. The second form opens the symbol toward larger values and reads the same when tested with 4 or any larger value. Rewriting to hold the variable on the left before testing reduces sign errors.
Why does my answer say x ≤ 5 but the graph looks like it runs left from 5?
The graph probably shows a filled circle at 5 with shading left, which is x ≤ 5. If your answer reads 5 ≥ x, it's the same statement with the variable on the right. Flip it to x ≤ 5 and the graph matches; if it doesn't, recheck whether the circle is filled or hollow.
What is the single most common mistake when reading these graphs?
Attaching the wrong symbol type to the circle — writing x < 2 for a filled circle at 2, when the correct reading is x ≤ 2. The symbol's direction is usually right; its strictness is what gets lost. Say "hollow means strict" once before writing the final answer.