The Bar Chart Maker accepts 2 to 30 strict "label,value" rows and produces a vertical bar chart whose category labels support up to 24 UTF-16 code units, whose numeric tokens support up to 40 characters of ordinary decimal or scientific notation, and whose exported SVG stays at 520 pixels tall while expanding horizontally as rows are added. Rotated category text keeps long phrases such as "Q3 Customer Satisfaction" legible without crowding neighboring bars, and the y-axis uses a 1, 2, 5, or 10 multiple of a power of ten as its upper bound so the scale reads cleanly on screen and in print. Five evenly spaced reference ticks expose the full range, and a tooltip on every bar reports its raw value, so even a bar drawn at the baseline still communicates its true height. Because one generated SVG string powers both the visible preview and the Blob download, the file you save matches the markup you reviewed. All parsing, scaling, escaping, and rendering happen in the current browser tab; no label, value, title, or SVG markup is uploaded.
What "Large Text" Actually Means for a Bar Chart Maker
Searchers looking for a bar chart maker that works with large text are usually solving one of three related problems: category labels that must stay readable when they are several words long, a chart destined for a slide, poster, or printed handout where every word needs to be visibly larger, or a tool that absorbs a sizable pasted dataset without choking. The Bar Chart Maker treats all three as a single problem and gives every category label up to 24 UTF-16 code units, rotates long labels for legibility, and lets the SVG expand horizontally as more rows arrive. The chart height stays fixed at 520 pixels so the proportions of the bars remain familiar across projects, while wide output scrolls horizontally inside the preview rather than packing 30 labels into a mobile width. Category slots remain separated throughout, which matters when text length varies row to row.
Row Format and Per-Field Length Limits
Every non-empty row must contain exactly one comma, with the label before it and a numeric token after it. The parser ignores blank or whitespace-only lines, trims leading and trailing whitespace around both the label and the number, and refuses the entire request if even one row is malformed. It does not keep only the first 30 rows, skip a bad row, substitute zero, or present a partial chart. Labels are measured in UTF-16 code units, the same way a browser counts characters for a textarea limit, and the strict cap is 24 code units. Numeric tokens are measured against a 40-character cap and may use ordinary decimals such as 12.5 or scientific notation such as 1.2e10. Quoted fields, quoted commas, additional columns, empty labels, typed units, expressions, hexadecimal, Infinity, and NaN are not supported. Duplicate labels remain separate bars in input order; the tool does not aggregate, sort, or infer units.
A short comparison helps clarify which inputs are accepted and which are rejected before you paste anything in.
| Input pattern | Result | Reason |
|---|---|---|
| label,value with one comma | Accepted | Strict CSV-lite row format |
| Empty value after the comma | Rejected | A numeric token is required |
| Label containing a comma | Rejected | Only one comma per row is allowed |
| Value in scientific notation (1.2e10) | Accepted | Ordinary decimal or e/E form is supported |
| Negative, Infinity, or NaN | Rejected | Values must be nonnegative finite base-ten |
| Label over 24 UTF-16 code units | Rejected | Strict label length cap; no truncation |
| 31 or more non-empty rows | Rejected | Hard cap of 30 non-empty rows |
| Duplicate labels | Accepted | Duplicate labels stay separate in input order |
Build the Chart From Large Text Labels
- Open the Bar Chart Maker and add an optional title in plain words. A blank visible title still receives the accessible label "Bar chart" so screen readers describe the figure.
- Paste 2 to 30 non-empty rows using the strict label,value form, with exactly one comma per row. Leading and trailing whitespace around each label and number is trimmed automatically.
- Click generate. The preview rebuilds with category labels, five evenly spaced reference ticks along the y-axis, a baseline at zero, and a tooltip on every bar that reports its raw value so a bar drawn at the baseline still communicates its true height.
- Verify the baseline sits at zero and the displayed axis maximum is the rounded 1/2/5/10 nice-domain upper bound.
- Download the standalone SVG. It is created from the exact string used to render the visible preview, so the file matches the markup you reviewed.
Rotated Labels, Tooltips, and an Expanding SVG
A vertical bar chart squeezed into a narrow viewport makes multi-word labels such as "Annual Subscribers" or "Top Referral Source" overlap their neighbors. To prevent that, the Bar Chart Maker rotates category labels so each line of text occupies its own slot rather than fighting for horizontal space. As you add rows beyond what fits comfortably, the chart expands horizontally inside the preview and scrolls; it never compresses the labels into a mobile width. Every accepted bar receives a tooltip that reports its raw value, which means even a bar drawn at the baseline still communicates its true height. Axis labels use up to six practical significant digits or scientific notation, and the upper bound is rounded to a finite 1, 2, 5, or 10 multiple of a power of ten. The result is a deterministic nice-domain chart that reads cleanly without promising to reproduce a particular D3 tick choice; for general guidance on selecting scales, see bar chart best practices for choosing scales and labels.
When Linear Scaling Makes a Bar Disappear
A linear ratio across an extreme range can be smaller than SVG coordinate precision. If you paste values such as 0.0001 and 1e12, the smaller bar will be drawn at the baseline even though the parser accepted it. The tooltip still reports its true value, and the chart will not invent a minimum-height bar because doing so would break the stated linear scale. All-zero data sets use an explicit zero-to-one reference range, keep every bar at zero height on the baseline, and display an all-zero note, an explicit decision to avoid division by zero rather than an inference that your data is missing. Nonzero values from 1e-300 through 1e300 are supported; lexical nonzero input that underflows to zero and input above the maximum are rejected. When tiny categories must remain visible beside values hundreds of orders larger, use a logarithmic or separately grouped chart instead; the Bar Chart Maker is built for linear comparison, not logarithmic compression.
Accessibility, XML Escaping, and the Standalone SVG
Every user string, including label, title, tooltip, and accessibility text, is XML-escaped before entering the SVG. Ampersands become entity references, angle brackets become < and >, and quotes and apostrophes are entity-encoded. XML-forbidden control characters and unpaired surrogates are replaced with U+FFFD, so a malformed paste cannot inject markup into the export. Numeric coordinates come only from validated finite values and are rounded to three decimals for the markup. The output uses the W3C SVG namespace and standard rect, line, text, g, and title elements as documented in the W3C SVG 2 specification. An accessible title element is always present even when the visible title field is left blank. Because the linear scale behavior follows the D3 linear scales reference for its 1/2/5/10 nice-domain approach, the chart remains predictable when you compare successive exports.
Common Large-Label Scenarios
Three patterns recur when category labels are long. Time series labels such as "January 2025 Sales" or "Q3 Customer Satisfaction" fit comfortably under the 24-character cap and rotate for legibility. Multi-word descriptive labels such as "Top Referral Source" or "Highest Bounce Rate Page" rotate for legibility under the same 24 UTF-16 code-unit cap as every other label. Codes and identifiers such as "SKU-9381-AB" or "REGION-NE-01" stay readable without rotation because they are short. If a label exceeds 24 code units, generation fails with an exact reason; the parser never truncates to fit. If you have more than 30 categories, generation fails with the exact non-empty row count, and the tool never silently keeps only the first 30. Negative zero is normalized to zero before rendering so a typographic artifact in your data does not affect the chart. Editing the title or data immediately clears the previous preview, status, and download to avoid stale Blob URLs.