How DatumParser Converts Excel Tables to AutoCAD (And Why It Looks the Way It Does)
If your converted drawing has a missing border, a wider-than-expected column, or a border that looks heavier than you'd expect — there's almost always a specific, deliberate reason. This page explains the common ones first, then goes into full detail below for anyone who wants the complete picture.
DatumParser reads your Excel file cell by cell, measures every piece of text with a real font before drawing anything, and only reproduces what Excel actually defines. Nothing is guessed or auto-decorated. If a cell has no border in Excel, it has no border in AutoCAD. If text needs more room than the column provides, the cell grows — the text is never cut off.
Common questions
A cell has text in Excel, but no border shows up around it in AutoCAD. Is that a bug?
No — this is expected. Each side of each cell is drawn only if Excel actually defines a border there. If a cell has text but no border formatting in Excel, it won't have one in the drawing either.
Why is one column much wider than I expected?
Almost always because a cell in that column has one long word or code with no spaces — a part number, a long identifier. AutoCAD can't break a single word mid-way the way Excel can, so the column widens to fit it fully rather than letting it overflow.
A border in AutoCAD looks unexpectedly thick. What's happening?
Check that cell's border style in Excel — thin, medium, thick, and double each map to a specific, increasingly heavy line weight in the drawing. A "thick" style in Excel will always produce a noticeably heavy line. That's the mapping working correctly.
Dashed or dotted borders show up as solid lines. How do I fix that?
This is a line-scale display setting in AutoCAD (LTSCALE), not a missing pattern. The drawing sets a scale meant to make these patterns visible at the table's size — if it still looks solid, that's the value to adjust.
I resized a text box in AutoCAD, and the text didn't reflow.
This only applies to cells that had "Wrap Text" on in Excel — those get a dynamic text box that reflows on resize. Cells without wrapping are drawn as a single line at a fixed size, so resizing the box afterward won't change how they wrap.
The table's size looks right, but something feels slightly off — a bit of extra space here or there.
Likely the text-measurement safety margin (see Text Measurement Accuracy below) — the tool errs toward a little extra room when it can't measure with full certainty against the exact font your AutoCAD installation uses.
Can I get a real double-line border, matching Excel exactly?
Not currently — double borders are drawn as a single, heavier line. A deliberate simplification to keep border rendering reliable rather than attempting true parallel lines.
Why didn't my chart, shape, or cell background color come through?
These are outside the tool's current scope — see What Doesn't Convert below for the full list.
The full picture
How sizing actually works
Most simple Excel-to-drawing conversions work "outside-in" — decide how big a cell should be from the column width, then hope the text fits. DatumParser works the other way:
- Read what's actually in the cell — the text, its font size, whether it's bold.
- Measure that text using a real font, to know exactly how much space it needs.
- Draw the cell at least as large as the text requires — starting from Excel's column width, growing it if needed.
The result: text should never be cut off, overlap a border, or spill into the next cell. If a column is wider than expected, it's very likely because something in it — often one long unbroken word — needed that room.
What converts
- Cell text and values, including numbers, dates, currency, and percentages
- Formatting: font size, bold, alignment, indentation, rotation, wrap
- Merged cells, in any direction
- Cell borders — style, weight, and pattern
- Images pasted directly into cells
What doesn't convert
These are outside the tool's current scope by design:
- Excel Shapes, SmartArt, and WordArt
- Native Excel charts and graphs
- Cell fill colors / background shading
- Formulas — only the calculated result is read, not the formula itself
About images: pasted images are saved as separate .png files alongside the .dxf, since DXF references images externally rather than embedding them. If you share the .dxf with someone, send the .png files with it, or the images won't appear on their end.
Number and text formatting
DatumParser reads Excel's actual cell format, not just the raw value:
| Format type | Example | Notes |
|---|---|---|
| Forced decimals | 0.000 → 1.500 |
Reads the exact decimal count from the format |
| Thousands separator | #,##0.00 → 1,234.50 |
|
| Currency | [$USD] #,##0.00 → USD 1,234.50 |
Preserves spacing between symbol and number |
| Percentages | 0.00% → 85.67% |
|
| Scientific notation | 0.00E+00 → 1.23E+08 |
|
| Fractions | # ?/? → 3 1/2 |
Denominator width follows the format |
| Zero-padded integers | 00000 → 00042 |
Pads to the exact defined width |
| Dates | Short and long form, including weekday/month names | See note below |
| Times | 24-hour and 12-hour | AM/PM calculated from the actual value |
| Negative numbers | -1,234.50 |
Always a minus sign — see Known Limitations |
Long date language: if your date format specifies a language explicitly in Excel, that language is used for weekday/month names. If the format uses a generic "system default" placeholder, there's no way to know the intended language from the file alone — DatumParser defaults to English.
Fonts and text sizing
All text is drawn in Times New Roman (regular and bold), matched to Excel's own default metrics — the specific font family used in Excel isn't reproduced. Bold cells use true Times New Roman Bold, not a scaled-up regular weight. Font size scales proportionally from Excel's own default (size 11).
Before drawing, DatumParser measures the exact width of each piece of text using the real font file — this is what makes the sizing approach above possible.
Text wrapping: rather than pre-computing line breaks, DatumParser gives AutoCAD's text a real-world box width and lets AutoCAD wrap it natively, the same as typing directly into AutoCAD. If you resize that text box later, it reflows automatically.
A word too wide for its column: since AutoCAD can't break a single word without a space, the cell widens to contain it fully rather than letting it overflow or get cut off.
Alignment (horizontal and vertical), indentation, and rotation (-90° to 90°, plus Excel's vertical "stacked" mode) are all reproduced from Excel.
Cell borders
Each side of each cell — top, bottom, left, right — is checked independently. A side with no border defined in Excel gets no border in the drawing, even if the cell has text or is part of a merged range. This is expected behavior, not a bug.
| Excel style | Drawn as |
|---|---|
| Hairline | Thinnest available line weight, solid |
| Thin | Thin solid line |
| Medium | Medium solid line |
| Thick | Thick solid line |
| Dotted | Thin, dotted pattern |
| Dashed | Thin, dashed pattern |
| Dash-dot / dash-dot-dot | Thin, matching dash pattern |
| Medium dashed / dash-dot variants | Same patterns, medium weight |
| Double | Approximated as a single medium-weight solid line |
If dashed or dotted patterns appear solid, it's almost always AutoCAD's line-scale display setting (LTSCALE), not a missing feature — the drawing sets a scale intended to make patterns visible at the table's size.
Text Measurement Accuracy
Text is measured using the real font file when available on the machine running the conversion. When it isn't, a close approximation with a built-in safety margin is used instead. In most cases this is invisible; occasionally, text sizing may be slightly more generous than strictly necessary.
Known Limitations
Being upfront about what DatumParser doesn't currently handle:
- Accounting-style negative numbers (shown in parentheses) aren't reproduced — negatives always use a plain minus sign.
- Rotated text combined with wrapped text in the same cell isn't supported — if both are set, only rotation is applied.
- Excel's "no leading zero" date/time codes aren't distinguished from padded equivalents — output is always zero-padded.
- Double borders are drawn as a single line, not two parallel lines.
- Column widths don't self-shrink the way row heights do, even around sparse content — intentional, since columns are shared across every table on a sheet, and auto-shrinking could remove spacing meant to separate unrelated tables sitting side by side.
- Shapes, SmartArt, WordArt, and native Excel charts aren't converted.
Have a file that didn't convert the way you expected? Let us know — DatumParser is in active development, and real examples help more than anything else.