In Power BI Desktop, go to the Visualizations pane → click the three dots → Get more visuals → search for Pareto Chart Pro.
Drag a category field (e.g. Customer, Product, SKU) into Entity and a numeric measure (e.g. Revenue, Quantity) into Value. The chart renders automatically with bars sorted from highest to lowest contribution and a cumulative line.
The left Y-axis shows each bin's share of the total. The right Y-axis shows the cumulative percentage. The default reference line marks the 80% threshold — the point where the top entities collectively reach 80% of the total value.
Add a hierarchy field (e.g. Category > Subcategory > SKU) to the Entity well. Use the drill buttons in the visual header to navigate levels.
| Field | Type | Description |
|---|---|---|
| Entity | Categorical / Hierarchy | The dimension to rank — e.g. Customer, Product, SKU, Supplier. Accepts a single field or a hierarchy for drilldown. |
| Value | Numeric measure | The metric to concentrate — e.g. Revenue, Units sold, Defect count. Must be a numeric aggregated measure. |
| Tooltips | Numeric measures (up to 10) | Additional metrics to display in hover tooltips — e.g. Profit, Margin %, Quantity, Order Count. |
| Setting | Default | Description |
|---|---|---|
| Bin size % Pro | 5% | Each bar represents this percentage of ranked entities. Range: 1–20%. Free tier is fixed at 20%. |
| Exclude bottom % Pro | 0 | Remove the lowest-value N% of entities before binning (outlier filter). |
| Exclude top % Pro | 0 | Remove the highest-value N% of entities before binning. |
| Bar color | #4472C4 | Fill color for all bars. Supports rule-based conditional formatting via the fx button; each bar takes the color of its top-ranked entity. |
| Bar opacity % | 85 | Opacity of bars (0–100). |
| Border color Pro | #2E5BA8 | Stroke color for bar borders. |
| Border width Pro | 0 | Stroke width in pixels (0 = no border). |
| Bar gap px Pro | 2 | Padding between bars in pixels. |
| IBCS Mode Free | Off | One-click toggle to apply International Business Communication Standards (charcoal neutral bars #404040, black solid axis typography, standardized contrast). |
Colors bars by where they fall relative to a cumulative % threshold. Overrides Bar color and any fx rule while it is on. Available in Free and Pro.
| Setting | Default | Description |
|---|---|---|
| Color bars by threshold | Off | Turns the whole card on. The remaining settings appear only when it is on. |
| Threshold (cumulative %) | 80 | The cumulative percentage that separates the vital few from the rest. |
| Within threshold | #4472C4 | Bars whose cumulative % is at or below the threshold. |
| Beyond threshold | #C6CFDF | Bars past the crossing bin. |
| Highlight crossing bin | On | Give the bin where the cumulative line crosses its own color. |
| Crossing bin color | #ED7D31 | Color for that bin. |
| Setting | Default | Description |
|---|---|---|
| Axis text color | #444444 | Color of axis tick labels. |
| Grid color | #e0e0e0 | Color of horizontal grid lines. |
| Font size | 11 | Axis label font size in points. |
| Show X axis label | On | Toggle the "% of entities (best → worst)" label. |
| Show Y axis label | On | Toggle the "% of total value" label. |
| Setting | Default | Description |
|---|---|---|
| Line color | #ED7D31 | Color of the cumulative percentage line. |
| Line width | 2 | Stroke width of the cumulative line in pixels. |
| Show dots | On | Show a dot at each bin's cumulative point. |
| Dot radius | 4 | Radius of the cumulative dots in pixels. |
Up to 3 reference lines, each configurable independently. Line 3 is Pro only.
| Setting | Default | Description |
|---|---|---|
| Show line 1 | On | Display the first horizontal + vertical reference crosshair. |
| Line 1 threshold | 80 | Cumulative % value where the line is drawn (0–100). |
| Line 1 color | #E84444 | Color of the reference line and labels. |
| Line 1 label | "80%" | Text label shown on the left Y-axis at the line. |
| Show line 2 / 3 | Off | Same settings as line 1, for additional thresholds. |
| Setting | Default | Description |
|---|---|---|
| Show | On | Display the percentage value above each bar. |
| Font size | 10 | Label font size in points. |
| Color | #444444 | Label text color. |
| Show % sign | On | Append "%" to the label value. |
The chart is a single Tab stop. Tab into it once and the arrow keys move between bins, so the chart never traps keyboard users the way a control with one stop per bar would.
| Key | Action |
|---|---|
Tab | Move focus into, or out of, the chart |
← → ↑ ↓ | Move between bins |
Home / End | First / last bin |
Enter or Space | Select the focused bin and cross-filter |
Ctrl / Cmd + Enter | Add the bin to the current selection |
Escape | Clear the selection |
Shift+F10 or ContextMenu | Open the context menu |
role="listbox" and each bar role="option" with
aria-selected kept in step with the actual selection.The visual ranks and bins in the browser, so what governs responsiveness is not the size of your model but how many entities end up behind a single bar. That number is entirely under your control: it is the total entity count multiplied by the bin size.
| Entities behind one bar | Imported model | Live connection |
|---|---|---|
| up to 5,000 | Immediate | Comfortable |
| 5,000 – 10,000 | Fluid | Slow but works |
| 10,000 – 20,000 | Perceptible, still usable | Not recommended |
| above 20,000 | Not usable — the visual declines to filter and tells you so | |
Every figure above was measured on a 500,000-entity model in Power BI Service with an integer key, varying bin size to vary entities per bar — on both an imported model and a live connection to a semantic model.
Clicking a bar asks Power BI to filter the rest of the report by every entity behind it. Power BI carries that as a list of values, and beyond roughly 20,000 the query it has to build becomes too large to run comfortably. So the rule is simply:
maximum bin size % = 1,000,000 ÷ number of entities
| Entities in the model | Largest bin size that stays filterable | Bars |
|---|---|---|
| up to 50,000 | 20% — no constraint | 5 |
| 100,000 | 10% | 10 |
| 250,000 | 4% | 25 |
| 500,000 | 2% | 50 |
| 1,000,000 | 1% | 100 |
A practical pattern for very large models: read the chart at a comfortable bin size, and drop to a smaller one when you actually want to click through to the detail.
In Power BI Service the visual streams data in segments and has been exercised at 500,000 entities with slicers re-ranking correctly. Power BI's own ceilings apply: 1,048,576 rows, and 100 MB of data, after which it stops sending more.
In Power BI Desktop segment streaming is unavailable and the visual stops at 30,000 rows. This is a Desktop platform behaviour, identical in Free and Pro.
Whenever Power BI stops short of the full set, the visual says so in an amber notice with the exact number of rows it received. A Pareto always spans 0–100%, so a chart built on partial data looks entirely normal — the notice is the only way to tell.
Keep the entity key narrow. An integer key costs far less than a long text code at every stage: less data to stream toward the 100 MB ceiling, and lighter filters when you click. If you have both, bind the numeric one.
| Feature | Free | Pro |
|---|---|---|
| Pareto chart with cumulative line | ✅ | ✅ |
| Reference lines (up to 2) | ✅ | ✅ |
| Bar color, opacity | ✅ | ✅ |
| Axis & grid styling | ✅ | ✅ |
| Cumulative line styling | ✅ | ✅ |
| Cross-filtering & multi-select | ✅ | ✅ |
| Drilldown / hierarchy | ✅ | ✅ |
| High contrast mode | ✅ | ✅ |
| Tooltips field well (up to 10 measures) | ✅ | ✅ |
| IBCS Mode (standardized styling) | ✅ | ✅ |
| Max entities (Power BI Service) | 500,000+ | 500,000+ |
| Bin size % (1–20%) | Fixed at 20% (5 bars) | ✅ Configurable 1–20% (up to 100 bars) |
| Outlier exclusion (top/bottom %) | ❌ | ✅ |
| Bar border & gap styling | ❌ | ✅ |
| 3rd reference line | ❌ | ✅ |
| Value labels on bars | ❌ | ✅ |
To activate Pro features, purchase a license from AppSource. License validation happens automatically inside Power BI — no configuration needed.
The visual always sorts automatically — you do not need to sort your data beforehand. If bars seem unsorted, check that:
Value field contains a numeric measure (not a text field or a calculated column).Line 1 is pre-configured to 80% by default. You can change it in Format Pane → Reference Lines → Line 1 threshold. Set the value to any cumulative percentage between 1 and 99. You can add a second line (e.g. 60%) and a third line at any value (Pro only).
License validation happens asynchronously after the visual first renders, so for a moment after opening a report the chart is drawn on the Free tier. Give it a second and it re-renders with your Pro settings applied. If it persists:
Every setting in the format pane is listed for all users, and the ones included in the Pro plan carry (Pro) in their name — bin size, outlier exclusion, bar border, bar gap, value labels and the third reference line. They are shown rather than hidden so you can see what the plan includes before deciding.
If you change one without a licence, the chart keeps rendering the Free result and Power BI shows its own notification with a link to get a licence. Nothing is lost: your setting is stored and takes effect as soon as the licence is active.
Add a hierarchy to the Entity field well (e.g. Product Category → Product Subcategory → SKU). The drill buttons appear in the visual header. Click the single arrow to drill down one level across all bins, or click a specific bar and use the fork arrow to drill into that selection. The Pareto recalculates automatically at each level.
Yes, from version 1.3.0.0. In Format Pane → Pareto → Bar color, click the fx button for the rule-based dialog — gradient, rules or field value, the same as a native visual.
One thing to understand about the result: Power BI resolves the rule per entity, but a bar is a bin holding many entities. Each bar takes the color of its top-ranked entity, falling back to the first entity in the bin that the rule resolves. So with a gradient, a bar shows where its largest member sits on the scale, not the average of the bin.
If what you want is to color bars by their position in the Pareto rather than by a field, use Threshold Colors instead — see below. It is usually the more useful of the two.
Format Pane → Threshold Colors colors each bar by where it falls relative to a cumulative percentage threshold — 80% by default. Bars within the threshold take one color, bars beyond it another, and the bin where the cumulative line actually crosses can be highlighted separately.
This answers the question a Pareto is usually asked: which share of entities is the vital few, and where exactly does the line cross? The fx dialog colors by a field value; Threshold Colors color by position in the distribution.
When both are on, Threshold Colors wins. The full precedence is: high contrast → IBCS Mode → Threshold Colors → fx rule → the constant Bar color.
This is usually a license assignment issue. Make sure the Pro license is assigned to the user account that is viewing the report in Power BI Service, not only to the account that published it. License assignment is managed in the Microsoft 365 admin center.
It depends on where the report runs:
Because entities are grouped into bins, size rarely hurts readability: 10,000 SKUs render as 5 bars at the Free 20% bin size, or 10 bars at a Pro 10% bin size. What size does affect is cross-filtering — see Performance & scale for how to choose a bin size for your model.
Yes. When Windows or Power BI high contrast mode is active, the visual automatically uses system foreground and background colors for all chart elements — bars, lines, axes, dots, and reference lines — to meet accessibility requirements.
No. All data processing happens locally inside Power BI. The only external network request is the license validation call to the Microsoft licensing API (IVisualLicenseManager) — this is the standard Power BI mechanism and shares no report data. See the Privacy Policy for full details.
Open an issue on GitHub. For billing questions or private inquiries, email us directly (see the contact section below). Please include your Power BI Desktop version, visual version, and a screenshot or sample .pbix if possible.
For bug reports, feature requests, and licensing questions:
support@tcviz.com
You can also open an issue directly on GitHub for bug reports and feature requests, or browse the Changelog to see what's new.