← Back to Tutorials

Engauge Digitizer Troubleshooting: 5 Common Problems & Fixes

⚡ Quick Answer

Most Engauge Digitizer problems have known fixes: missing points on export → switch the curve from Function to Relation; freezes on log-axis export → export linear and convert in your spreadsheet; shifted dates → digitize on a numeric axis and convert later; scientific-notation axes rejected → type decimals like 0.001; tracer grabbing gridlines → zoom in, filter by color, or erase gridlines first.

Problem 1: Points Missing from the Exported CSV

You traced 200 points, but the CSV has 120. The usual culprit is the Function vs Relation curve setting: a Function keeps only one Y per X value, so any part of the curve that doubles back gets its extra points silently dropped.

  1. Check the curve type: Open the curve settings (select the curve in the Curves List) and look for the Function/Relation option.
  2. Switch to Relation: Set it to Relation, which allows multiple Y values per X.
  3. Re-export: File > Export again and compare the point count — it should now match what you traced.

Problem 2: Freeze or Hang on Logarithmic Export

Exporting dense curves on log scales is a known weak spot — users report hangs, especially on log-log plots. Two workarounds:

  • Thin the points first — fewer points export more reliably; you rarely need 1,000 points for a smooth curve.
  • Export linear, convert later — temporarily treat the axis as linear, export, then take log10 of the values in Excel or Python. The math is identical; the exporter just never sees a log axis.

Problem 3: Dates Shifted After Export

If your time axis comes out offset by hours, Engauge’s date/time handling applied a timezone conversion you didn’t ask for. The robust fix: don’t digitize on a date axis at all — set up a plain numeric axis (hours or days since the start), export numbers, and convert to real dates in your spreadsheet where you control the timezone explicitly.

Problem 4: Scientific Notation Rejected on Axes

Axis values like 1e-3 or 2.5E6 may fail to parse when you place axis points. Simply type the decimal form — 0.001 instead of 1e-3, 2500000 instead of 2.5E6. Pick gridlines whose decimal values are easy to write out.

Problem 5: Auto-Tracer Grabs Gridlines

The tracer follows contrast, and a dark gridline next to your curve is irresistible to it. Fix it in this order:

  1. Zoom in: Work in the zoom window so the curve and gridline are clearly separated pixels.
  2. Filter by color: If your curve is blue and gridlines are gray, Segment Fill with a color filter locks onto the curve only.
  3. Erase first: Use the eraser tool to remove gridline segments near the curve before tracing.

⚠️ Note: Still stuck? Check whether the issue is already reported on the Engauge Digitizer GitHub repository — several of the issues above come straight from its tracker, and the maintainer responds there.

Related Guides

How to Digitize Logarithmic Axes

Log-scale setup done right, so export behaves.

How to Digitize Multiple Curves

Segment Fill and Point Match for multi-curve figures.

Is Digitized Data Accurate Enough to Publish?

Validation evidence and best practices.

Frequently Asked Questions

Why are points missing from my exported CSV?

The most common cause is the curve’s Function vs Relation setting. A curve set to “Function” keeps only one Y value per X — so if your curve doubles back (two Y values for one X), the extra points are silently dropped on export. Open the curve settings and switch it to “Relation”, then export again.

Engauge Digitizer freezes when I export on logarithmic axes. What can I do?

This is a known pain point with log-scale export on dense curves. Workarounds that users report as reliable: reduce the number of digitized points before exporting, or export the curve on a linear scale and convert to log values in your spreadsheet (take log10 of the exported numbers).

My dates come out shifted by hours after export. Why?

Engauge’s date/time axis handling can apply timezone conversions, shifting your timestamps. If exact times matter, the safest workaround is to digitize against a plain numeric axis (e.g. days since start) and convert to dates in your spreadsheet, where you control the timezone.

Engauge won’t accept axis values like 1e-3. How do I enter scientific notation?

Type the decimal equivalent instead — 0.001 rather than 1e-3. Place your axis points on gridlines whose decimal values you can write out plainly, and the calibration will be exact.

The automatic tracer keeps grabbing gridlines instead of my curve. How do I fix it?

Three fixes, in order: (1) zoom in so the curve is clearly separated from gridlines; (2) use Segment Fill with a color filter if your curve has a distinct color; (3) use the eraser to remove gridlines near the curve before tracing. Thick gray gridlines are the #1 cause of bad auto-traces.

Ready to try it yourself?

Download Engauge Digitizer free and follow along with this guide.

Download Engauge Digitizer