Export Research Figures with Reproducible Size and Content

Treat the exported figure as an analysis artifact

A screenshot of an interactive window may be difficult to reproduce and can omit labels or alter resolution. Save the figure from code using explicit dimensions, output format and relevant rendering settings. Keep the plotted data and transformation code associated with that output version.

The Matplotlib savefig documentation describes format, resolution, bounding-box and metadata options. Choose them according to the destination’s requirements while checking the actual exported file, not just the in-memory preview.

Match format to content

Vector output can preserve sharp lines and text for many statistical graphics, while raster output has a fixed pixel grid. Complex raster images embedded in a vector file do not become infinitely detailed. Confirm font handling and whether the receiving application changes symbols, line widths or transparency.

Specify physical dimensions before choosing text size. A figure that is legible at full-screen width may become unreadable when placed in a single journal column. Avoid compensating for a crowded design solely by increasing resolution; more pixels do not make tiny labels easier to read at the same physical size.

Check a hypothetical raster export

Suppose a figure is intended to be six inches wide at 300 dots per inch. Its raster width should be 6×300 = 1,800 pixels. If the exported image is only 600 pixels wide and placed at six inches, its effective resolution is 100 pixels per inch.

That arithmetic checks file dimensions, not visual quality or compliance with every journal rule. Inspect labels, markers and thin lines at the intended display size. A numerically sufficient image can still have clipped legends, overlapping annotations or misleading axis limits.

Verify the final artifact

Reopen the exported file independently of the plotting session. Compare its data values, limits and legend with the source result table. Check that bounding-box cropping has not removed a panel label and that background transparency behaves correctly on the destination page.

Store the script, environment information, figure-data version and export settings together. Use a stable filename or manifest linking the figure to the manuscript version. The deliverable should be both visually usable and regenerable, so a later correction to an estimate can update the figure without reconstructing undocumented manual edits.

Source verification: 6 November 2026. Examples are hypothetical.