This guide explains VLOOKUP and HLOOKUP in plain, simple language, with worked examples built one step at a time rather than assuming prior formula experience. It's written for anyone learning these formulas for the first time, regardless of which language they usually work in day to day.
Both formulas do the same basic job - matching a value and returning related data - the only difference is whether your data is arranged in columns or rows.












VLOOKUP means "vertical lookup." It looks down a column for a value you give it, and once it finds a match, it returns a value from another column in that same row.
| Employee ID | Name | Department | Salary |
|---|---|---|---|
| E101 | Asha Rao | Marketing | 54000 |
| E102 | Vikram Shah | Finance | 61000 |
| E103 | Priya Nair | Sales | 48000 |
HLOOKUP works the same way, except it looks across a row instead of down a column. It's used when your categories are listed across the top instead of down the side.
| Metric | Q1 | Q2 | Q3 |
|---|---|---|---|
| Revenue | 210000 | 245000 | 238000 |
| Expenses | 150000 | 162000 | 158000 |
- What to search for - a value like an ID or a quarter label.
- Where to search - the full data range, including the row or column with the values you want back.
- Which row or column to return - counted from the start of the selected range.
- TRUE or FALSE - almost always FALSE, meaning an exact match is required.
The most frequent mistake beginners make with either formula is forgetting to set the last argument to FALSE, which can cause Excel to quietly return an approximate match instead of flagging that no exact match exists.
Turbo Excel VLookup performs the same kind of matching without requiring either formula to be typed - you select the matching columns from dropdown menus and the app applies the match across the whole dataset automatically.
A surprising number of VLOOKUP problems turn out to be a data type mismatch rather than a logic error - a value stored as text in one column and as a number in the other will never match, even if they look identical on screen.
Before assuming the formula itself is wrong, select the lookup value's cell and check the small green triangle or the number alignment; numbers align right by default, and text aligns left, which is a fast way to spot the mismatch.
In a shared workbook, a bare VLOOKUP formula gives the next person no indication of what it's supposed to be matching or why. Adding a cell comment, or a short label in an adjacent column, explaining the source and purpose of the lookup saves significant time when the workbook is revisited months later or handed to a colleague.
This becomes even more important once a workbook has several lookups feeding into each other, since untangling a chain of undocumented formulas is far harder than reading a documented one.
What is the simplest way to understand VLOOKUP?
It searches down a column for a value and returns data from another column in the same matching row.
What is the simplest way to understand HLOOKUP?
It works the same as VLOOKUP but searches across a row instead of down a column.
Why is FALSE important in both formulas?
It requires an exact match, which avoids Excel silently returning the wrong, approximate result.
Do I need advanced Excel knowledge to use these formulas?
No, both formulas only require understanding four arguments filled in a fixed order.
Which formula should a beginner learn first?
VLOOKUP, since most spreadsheets are organized in a column layout that fits VLOOKUP more naturally.
Is there an option that avoids typing either formula?
Yes, Turbo Excel VLookup matches data through a simple dropdown-based interface instead of a formula.
Does the order of rows in the source data matter for an exact match?
No, an exact match search works regardless of row order; only an approximate match requires sorted data.
Is it safe to have duplicate values in the lookup column?
A lookup formula will only return the first matching row it finds, so duplicates can silently return the wrong record if not accounted for.
Should I test a new formula on one row before applying it everywhere?
Yes, verifying a single result against the source data first catches setup mistakes before they're copied across an entire column.
Is it a good idea to edit source data while formulas are actively referencing it?
It's safer to keep a stable source sheet separate from a working sheet, since editing referenced data mid-use can produce confusing intermediate results.
Ready to stop fighting #N/A errors and match your spreadsheets visually?