You opened a spreadsheet, stared at thousands of rows, and asked the question every Excel user eventually faces. How many records match more than one rule at the same time? The COUNTIFS function is the answer.
It counts cells across one or more ranges, but only when every criteria you pass holds true. Where COUNTIF can only juggle a single condition, COUNTIFS chains as many as 127 — sales by region and quarter, students passing both math and reading, orders that shipped in March from a specific warehouse. It is the workhorse behind dashboards and audit reports.
This guide walks through the function the way a working analyst uses it. You'll see the exact syntax, when wildcards earn their keep, how date ranges actually behave, and the silent bugs that make your totals look fine while quietly being wrong. We cover errors you'll meet (and how to fix them in seconds), the difference between COUNTIFS and SUMPRODUCT, and the moment when a PivotTable beats both. If you want to test yourself afterwards, jump into our Excel practice test — every question mirrors what employers actually grade in interviews and certifications.
COUNTIFS takes pairs. Each pair is a range and a matching criteria. The signature reads =COUNTIFS(criteria_range1, criteria1, [criteria_range2, criteria2], ...) — square brackets mean optional, and you can add up to 127 of them. Every range must be the same size. If your first range is A2:A100, every other range needs to span 99 cells too. Mismatch the dimensions and Excel returns #VALUE! without explanation.
Criteria can be a number (50), text in quotes ("Active"), a comparison string (">=100", "<>Closed"), a cell reference (F2), or a wildcard pattern ("*pending*"). Excel is not case-sensitive when matching text, so "YES" equals "yes" equals "Yes". This is a feature when you're cleaning messy data and a footgun when you actually care about case.
Just type the value. Equal-style criteria like "Approved" count rows where the cell exactly equals that string. No operator means equality.
Wrap in quotes: greater-than 100, less-than-or-equal a date, not-equal-to zero. Operators include >, <, >=, <=, =, and <> (not equal).
Use F2 or concatenate operators with & to make criteria dynamic — change the input cell, watch every count update across the workbook.
Imagine an order log with columns for region, product, units sold, and ship date. Your manager wants to know how many orders shipped at least 50 units of "Widget A" from the West region during Q1. Three conditions, one cell. The formula reads =COUNTIFS(A2:A1000, "West", B2:B1000, "Widget A", C2:C1000, ">=50", D2:D1000, ">=2026-01-01", D2:D1000, "<=2026-03-31").
Notice the date range trick. COUNTIFS has no native "between" — you fake it by passing the same range twice with opposite operators. The result is one number, fast, even on a million rows, because the function is optimized at the engine level. Anyone updating the source data will see the count refresh instantly. If you instead want to break that count out by region without writing five formulas, you may want a PivotTable; we'll come back to that.
To count rows where a date falls in a window, pass the same date range twice with opposite operators (greater-than-or-equal Start, less-than-or-equal End). StartCell and EndCell can hold real Excel dates — no string parsing required.
Wildcards: ? matches one character, * matches any number. To count rows where column B contains the word "urgent" anywhere, wrap the keyword in asterisks. Case is ignored. To match a literal asterisk or question mark, escape with a tilde.
Use not-equal-to followed by the value to exclude. To count any non-empty cells in a range, use not-equal-to with an empty string. That last form is the cleanest way to count rows with any value at all.
COUNTIFS uses AND by default. For OR — say, count rows where region is West or East — sum two COUNTIFS calls, or use a SUM with an array constant of the two values inside the criteria slot. Both approaches return the same total.
Wildcards are powerful and easy to misuse. The asterisk is greedy — a pattern like "sales*" matches "sales", "salesperson", and "sales report 2026" alike. If you want exactly "sales" and nothing else, drop the wildcard. People often forget this and wonder why their count is triple what they expected.
Numbers do not respond to wildcards. A pattern like "1*" against a numeric column returns zero matches because Excel sees numbers as numbers, not strings. To filter numeric ranges, use comparison operators like greater-than-or-equal or less-than, or convert the column to text first. The same rule applies to dates — they are numbers under the hood, formatted to look like 2026-05-14.
Before trusting any COUNTIFS result, do two things. First, swap COUNTIFS for COUNTA on the same source range. Your COUNTIFS answer should be less than or equal to COUNTA. If it's greater, you have duplicate criteria ranges or pointing errors. Second, manually filter the data with Excel's filter dropdown using your conditions and check the row count in the status bar. If both numbers agree, ship it.
Three errors show up over and over. #VALUE! means your ranges are different sizes — line them up. #NAME? means you typed COUNTIF instead of COUNTIFS, or there's a typo. #DIV/0! doesn't come from COUNTIFS itself, but it will appear if you wrap COUNTIFS in a division (averaging) and the denominator hits zero. Wrap with IFERROR for safety, returning zero when the inner expression fails.
A subtler bug is silent zero. You'll get a count of zero when criteria look right but data is stored as text instead of numbers — common when importing CSVs. Convert the column with VALUE or by multiplying by 1, then re-run. Likewise, leading or trailing spaces in text columns wreck exact matches. Use TRIM on a helper column or run Find & Replace to clean the source.
If you want to sum values that meet criteria — not just count them — switch to SUMIFS. Syntax is nearly identical, but the first argument is the range you're summing. Same wildcard rules, same date trick, same speed. Reach for it the moment your manager asks "how much" instead of "how many".
SUMPRODUCT can do everything COUNTIFS does and more, including OR logic in a single formula, but it does not short-circuit and gets noticeably slower at scale. Use it when you need conditions that COUNTIFS cannot express — boolean math, lookups, or counting unique values. For everyday filtering, COUNTIFS is faster, clearer, and easier to audit.
For exploratory work, a PivotTable blows past both. You get cross-tabs, subtotals, and drill-down without writing a single formula. Rule of thumb: COUNTIFS for dashboards and reports that recalculate live; PivotTable for ad hoc analysis. Many analysts use both side by side.
Three small changes can cut a slow workbook's calc time by 80 percent. First, convert your data range into a Table (Ctrl+T) and reference it by name — Table-aware formulas evaluate only the populated rows, not the whole column. Second, avoid INDIRECT inside criteria; it is volatile and forces recalculation on every change. Third, when you need the same count repeated across hundreds of cells, calculate it once in a helper cell and reference that cell.
If you're on Excel 365, the FILTER function combined with ROWS() can sometimes outperform COUNTIFS for very complex predicates because it evaluates lazily. Test both on your real data before committing — "faster" depends on your row count, column count, and whether your workbook has volatile formulas elsewhere.
HR reporting: Count employees in the Engineering department hired after 2024 who are still active. Three criteria, one cell, one number that updates the moment HR onboards a new hire. The same template extends to compliance audits, headcount forecasts, and turnover dashboards.
Sales operations: Pipeline-by-stage counts feed weekly forecast meetings. A single COUNTIFS pulls how many deals are in Negotiation, owned by a specific rep, expected to close this quarter. Drop it across a grid of reps and stages and you have a one-page pipeline review.
Quality assurance: Count defects logged in the last 7 days, severity High or Critical, in modules tagged Production. The result drives the daily standup. Pair it with conditional formatting to highlight cells that cross a threshold, and the number tells a story without anyone having to read it.
Concatenate an operator inside quotes with a cell reference using the ampersand. Static formulas become interactive dashboards in one stroke.
Name your data ranges so formulas read like sentences. Six months later, you'll still understand what the COUNTIFS is doing.
Convert with Ctrl+T. Structured references plus auto-expanding ranges eliminate "forgot to extend the formula" bugs forever.
If you're prepping for the Microsoft Office Specialist (MOS) Excel exam, the Excel Associate exam, or any analyst interview screen, COUNTIFS is one of the half-dozen functions you absolutely must demonstrate live. Examiners ask for it explicitly, and they ask for the date-range trick, the wildcard trick, and the OR workaround. Knowing the formula is the floor — speed and confidence under timed conditions are the ceiling.
Our Excel practice test targets exactly these patterns. You'll see questions on multi-criteria counting, errors, wildcards, and the COUNTIFS vs SUMIFS choice. Every question includes a hint and a worked explanation. Knock out a 20-question set, identify gaps, and circle back here for the fix. Most people see their score jump 15 points after a single focused session.
Once you have the basics down, a handful of advanced patterns separate hobbyists from working analysts. The first is concatenating dynamic operators with cell references. Instead of hard-coding the threshold, you write the operator inside quotes, then bolt the cell reference on with an ampersand. This pattern is the bridge between static reports and interactive dashboards — a single input cell drives every count on the page, which is exactly how stakeholders expect a modern report to feel. Change the date in F1 and watch all 40 counts on the dashboard refresh in a heartbeat.
The second advanced move is using named ranges. Naming your data ranges (Insert > Name > Define) makes formulas self-documenting and immune to inserted columns. A formula that reads COUNTIFS(SalesRegion, "West", SaleAmount, greater-than 1000) explains itself. Six months from now, when you or a teammate reopens the file, the meaning is obvious. Compare that to a formula referencing A2:A1000 and C2:C1000, and you'll never go back. Named ranges are also faster to type, easier to audit, and cleaner in error messages when something goes wrong somewhere upstream in the workbook.
The third move is leveraging Excel Tables. Convert your dataset with Ctrl+T, give the table a name, and your COUNTIFS automatically references the active range — no "forgot to extend the formula" bugs ever again. Tables ship with structured references, banded rows, automatic filter buttons, and total rows that calculate aggregates without writing a single formula. They also play well with PivotTables, Power Query, and conditional formatting. If your dataset is going to grow over time, converting it to a Table is the single highest-leverage change you can make in Excel.
Every analyst eventually meets a COUNTIFS that refuses to return the expected number. The fastest debugging path is to isolate one criterion at a time. Comment out (or remove) all but the first criteria pair and check the count — should be high but reasonable. Add the second pair, recount. Add the third. The criteria that drops the count to zero is the bug. From there, examine the source data for that specific column: are values stored as text, are there hidden characters, is your operator string formed correctly?
A surprising number of bugs come from regional settings. If your file was created on a European Excel install and opened in a US install, the list separator may have flipped between comma and semicolon, dates may have flipped between DD/MM/YYYY and MM/DD/YYYY, and decimal commas may be invisible until you click a cell.
Open the cell in formula bar view and check what's actually there — the displayed value can lie. Format the column as a number and the text-stored ones will not realign. Format as a date and the strings will refuse to display correctly. Both signals tell you what to fix.
For very stubborn problems, build a parallel helper column with simple IF logic mimicking your COUNTIFS criteria — one column per criterion, then a final column with AND across them. Sum the final column. If the helper-column total matches your COUNTIFS, the function works fine and your understanding of the criteria is wrong.
If they disagree, you've localized the bug to a specific criterion. This technique sounds like a lot of work for a function that should "just work", but on a deadline it can save an hour of staring at the formula bar wondering why the answer is 7 instead of 47.
COUNTIFS rarely lives alone. The moment you start building real dashboards, you'll chain it with other functions to express ideas the basic syntax cannot capture. Wrapping COUNTIFS in IF lets you show different text based on threshold counts — "on track", "watch", "behind" — which is exactly what executives want to see at a glance. Dividing one COUNTIFS by another, you compute conversion ratios, completion rates, and segment shares without leaving the cell. These derived metrics often matter more than the raw counts, and they all build on COUNTIFS as the foundation.
Paired with TEXTJOIN, COUNTIFS can build dynamic labels like "42 active accounts in West region (Q1 2026)" — a single cell that updates as the underlying numbers shift. Paired with INDEX/MATCH or XLOOKUP, COUNTIFS can drive lookups whose results depend on whether enough matching records exist. Paired with conditional formatting rules, a COUNTIFS in a helper column can color-code rows based on whether they meet multiple criteria at once. Each combination is a small idea, but together they form the vocabulary of professional spreadsheet work.
One pattern worth knowing well is the running-count technique. Place COUNTIFS in column C with the criteria_range starting at row 2 and extending only to the current row. As you copy the formula down, each cell counts matches from the top of the data through its own row, creating a running count of records meeting your conditions. The same idea generates row numbers within a category — "this is the third Widget A order this month" — which feeds into ranking, deduplication, and time-to-event analysis without needing a single PivotTable or VBA macro.
If you're prepping for an analyst interview, you can expect at least one COUNTIFS question. Sometimes it shows up as a take-home exercise. Sometimes it's a live whiteboard scenario where the interviewer reads off conditions and watches you build the formula. The classic prompt: "Given a sales table, count the number of orders placed by customers in California for products in the Beverages category where the order value exceeded 500 dollars during the last quarter". Four criteria, one COUNTIFS, easy to write if you've practiced. Stumble on the date-range trick and you signal inexperience.
A common follow-up: "Now do the same thing but include both California and Oregon". The interviewer is testing whether you know COUNTIFS handles AND only. The right answer is either two COUNTIFS added together or a single SUM-of-COUNTIFS with an array constant. Either answer is fine — the interviewer is checking that you recognize the limitation and have a fix. Memorize both forms before any interview involving Excel skills, even at the analyst level.
A trickier variation: "Count only the unique customers who placed at least one order meeting these criteria". This one COUNTIFS cannot handle alone. The proper answer involves SUMPRODUCT with 1/COUNTIFS, or in Excel 365, UNIQUE combined with FILTER. Don't fake it — say "COUNTIFS counts rows, not unique values, so I'd reach for UNIQUE and FILTER here" and you've demonstrated real understanding. Interviewers love that kind of clarity. Hand-waving past the limitation costs you the role.