Pictogram Chart: Definition, Examples, and Best Practices

Pictogram charts offer a simple way to visualize discrete, countable data like headcount, deals closed, or units shipped. This guide walks through the definition and variations of pictogram charts, provides worked examples with the math behind icon counts, and shares design standards and accessibility requirements to help you build visualizations that communicate clearly without sacrificing credibility.

Key takeaways

If you want pictogram charts that people actually trust and act on, focus on these basics:

What is a pictogram chart

A pictogram chart uses repeated icons to represent quantities. Each icon stands for a specific number of units. Viewers count icons to understand totals. You might also hear this called a pictograph, picture chart, or pictograph chart (all these terms mean the same thing).

Bar charts encode value through length. Pie charts use angles. Pictograms? They rely on simple counting. A row of five person icons where each icon equals 10 employees tells you there are 50 people in that department. No axis interpretation required.

One quick, important clarification: Pictogram charts have nothing to do with the Globally Harmonized System of Classification and Labelling of Chemicals (GHS) or Occupational Safety and Health Administration (OSHA) hazard pictograms. Those diamond-shaped chemical safety symbols serve an entirely different purpose. This guide covers data visualization only.

When to use a pictogram chart

Instant comprehension over precision. That's the trade-off pictograms make, and they make it well under specific conditions.

Your data should be discrete and countable. Whole units like people, products, customers, or locations fit perfectly. Percentages and continuous measurements do not.

Seven or fewer categories keeps things scannable. Push past that limit and visual clutter starts working against you.

Value ranges matter too. If your largest number requires more than about 40 icons, the chart becomes tedious. At that point, a bar chart gets you the comparison with less visual effort.

And your audience? Pictograms reward the glance. They are built for people who will look at your chart for seconds, not minutes. Executives scanning a dashboard before a leadership meeting. Sales or operations managers checking headcount or deal counts. Frontline teams who just want to see exactly how many, at a glance, without needing a data translator.

If you spend a lot of time re-explaining the same key performance indicator (KPI) chart to nontechnical stakeholders, you're not alone. Sixty percent of respondents report a data skills gap. That statistic explains why pictograms often outperform more complex charts: When your audience lacks data fluency, the visual has to do more of the work.

When precision matters, pictograms will let you down. If stakeholders want to distinguish between 847 and 852, the rounding required for icon counts will obscure that difference entirely.

Pictogram chart examples with calculations

Most pictogram tutorials show you finished charts without explaining the math. Here's how the conversion actually works.

Consider employee headcount across four departments: Sales has 45 people, Engineering has 78, Marketing has 32, and Support has 56.

Start by finding your key. Take the largest value (78) and divide by your target icon count. Aiming for eight to 12 icons per row keeps things readable. So 78 divided by 10 gives you 7.8. Round to a clean number. Your key becomes 10, meaning each person icon represents 10 employees.

Now convert each department. Sales gets 4.5 icons. Engineering gets 7.8. Marketing gets 3.2. Support gets 5.6.

Partial icons create the real challenge. It's where a lot of people trip up. Applying thresholds inconsistently across categories or changing them mid-project will undermine trust sooner than you'd expect. Pick your rounding rules once and stick with them throughout the entire visualization. A reliable approach uses these thresholds:

So Sales displays four full icons and one half icon. Engineering shows eight full icons. Marketing gets three full icons. Support shows six full icons.

Always disclose your rounding policy in a footnote.

Pictogram chart variations

Three variations change how viewers interpret the data. Everything else is cosmetic.

Icon arrays for part to whole comparisons

An icon array arranges icons in a fixed grid, typically 10 by 10 for 100 total. Filled icons show the proportion. If 63 icons are filled out of 100, that's 63 percent.

Standard pictograms use each row for a different category. Icon arrays show one metric as a proportion rather than comparing multiple categories. Icon arrays work best when your data naturally converts to a clean percentage. If you're forcing awkward conversions (say, showing 47.3 percent as 47 icons), you might be better served by a different chart type.

Scaled icons and why to avoid them

Some pictograms vary icon size to show magnitude. Bigger icon, bigger value.

This approach misleads viewers because humans misjudge area. An icon twice as tall appears four times as large. Viewers systematically misread the relative values. The fix is straightforward: vary the count, not the size.

Icon grids for benchmark comparisons

To show progress toward a target, use filled icons for actual values and outlined icons for the gap. Seven filled icons and three outlined icons shows 70 percent progress toward a goal of 10.

This pattern works well for quota tracking, fundraising progress, or capacity utilization.

Design standards and quality checklist

Every rule here prevents a specific type of misreading.

If the pictogram chart is part of a governed dashboard, treat the legend, rounding note, and metric definition as a package. People trust the visual more when they can trace it back to an approved metric, not a one-off calculation sitting in somebody's slide deck.

How to create a pictogram chart

The workflow stays consistent whether you're using Excel, Google Sheets, or PowerPoint.

If you build pictogram charts inside a BI platform, the logic stays the same. The big difference is operational: You can keep the chart connected to governed data sets and distribute it in role-specific dashboards. No more rebuilding icon math every time someone asks for "the same chart, but for my region."

Step 1: Prepare the data

Structure your data with one column for categories and one for counts. If your source contains decimals, decide now whether to round before visualization or handle partial icons.

Sorting categories by count in descending order often improves readability.

Step 2: Choose an icon and define the key

Pick an icon that represents what you're counting. Person icons for headcount. Box icons for shipments. Deal icons for closed-won opportunities. Avoid abstract shapes that need explanation.

Calculate your key by dividing the largest value by your target icon count. Eight to 12 icons per row works well.

Step 3: Map values to icons

Divide each category's count by the key. Apply your rounding thresholds for partial icons. Document your rounding policy.

Step 4: Add labels and validate

Place the legend where viewers see it first. Top left or directly below the title works.

Run a validation check before publishing. Multiply your icon count by the key for each category. The result should closely match your original values.

Step 5: Export and check accessibility

Scalable Vector Graphics (SVG) format gives you scalable, crisp icons. Portable Network Graphics (PNG) works for fixed sizes but loses quality when resized.

For accessibility, add alt text that describes the insight, not just "pictogram chart." Ensure icon-to-background contrast meets a 4.5 to 1 ratio. Provide a companion data table for people who use screen readers.

Limitations and alternatives

Pictograms trade precision for instant comprehension. When that trade works against your goal, switch chart types.

For recurring reports where maintenance matters, bar charts update automatically without manual icon math. For one-time presentations to nontechnical audiences, pictograms deliver higher visual engagement.

Tool sprawl is another thing to watch. When your main BI tool doesn't offer pictogram charts and teams build icon charts in external tools, metric definitions, rounding rules, and filters can drift across departments. That's a fast path to "Why doesn't your number match my number?" in the next exec review. I've seen it happen more than once.

Accessibility and inclusive design

Generic advice about colorblind-safe palettes isn't enough. 95.9 percent of homepages on top websites fail the Web Content Accessibility Guidelines (WCAG). That number matters because it means even well-intentioned teams routinely miss accessibility requirements. You need specific thresholds.

Thin, minimalist icons often disappear on high-resolution screens. Test your chosen icon at actual display size before building the entire chart.

If your audience reads dashboards on phones (field teams, store managers, traveling execs), double-check icon size and spacing on mobile. Pictograms can look great on a big screen and turn into confetti on a small one.

Templates and pictogram maker guidance

If you're choosing between spreadsheets and Domo for pictograms, focus on a few practical checks:

If your team already builds dashboards in Domo, keeping icon-based visuals in the same BI environment will help reduce rework. You can publish the same visual to role-specific views for executives, managers, and day-to-day teams, while keeping definitions tied to governed data. That helps analysts spend less time explaining charts and more time answering higher-value questions.

For teams that want pictogram charts outside internal dashboards, Domo Embed supports embedded analytics. You'll be able to place interactive pictogram chart visualizations in a customer portal, a software-as-a-service (SaaS) app, or even a public web page, then keep the styling consistent with a Brand Kit (colors, fonts, logos). You can also reuse a single pictogram chart template across segments with dynamic data set switching, and control what data appears for each person with programmatic filtering (pfilters).

For teams building pictograms occasionally, Excel or Google Sheets with manually placed icons works fine. For recurring reports, a BI tool with native pictogram support eliminates the repetition. In Domo, you can keep icon-based visuals alongside your other dashboard charts, so updates follow the same data sets and governance rules.

If you want to swap "why doesn't your number match my number" for governed, repeatable pictograms your stakeholders will trust, compare notes with people building these charts in production reporting. Join the Domo community.