How Do Plt Subplots Figsize And Dpi Interact?

Okay, let me walk through this more methodically — there are a few gotchas I learned after ruining a poster layout once. First, figsize=(width, height) describes the physical page size in inches for the entire figure. If you create subplots with plt.subplots(nrows, ncols, figsize=(8,6)), that 8×6 inch rectangle is split among all the axes plus margins. dpi multiplies those inches into pixels: (8*dpi, 6*dpi). So when you increase the number of subplots, either increase figsize or increase dpi to keep the same pixel density per subplot.

Second, remember the distinction between onscreen rendering and saved output. The figure object has fig.dpi, but plt.savefig(..., dpi=...) can override that for exports. Many people prefer to design at a comfortable figsize and modest dpi (e.g., 100) for interactive work, then export at higher dpi (e.g., 300) for print. Also, fonts are measured in points (pt), not pixels — a 12 pt font corresponds to 12/72 inches — so changing dpi affects pixel count but not the inch-size of fonts; higher dpi just renders the same physical size with more pixels (sharper).

Finally, if you need consistent output across systems, set rcParams like plt.rcParams['figure.dpi'] and plt.rcParams['savefig.dpi'] and use fig.set_size_inches(...) if resizing programmatically. For publications, prefer vector outputs (pdf/svg) unless you have complex raster layers. Little adjustments to subplot spacing (tight_layout or constrained_layout) often matter more than tiny dpi tweaks, so I usually iterate a couple of exports until everything lines up cleanly.

Oh man, fiddling with figsize and dpi in plt.subplots is one of those tiny pleasures that makes a figure go from meh to crisp. At the core it's simple math: figsize is in inches, dpi is dots (pixels) per inch, so pixel dimensions = (width_inches * dpi, height_inches * dpi). For example, fig, axes = plt.subplots(2, 2, figsize=(6, 4), dpi=100) results in a 600×400 pixel canvas. That total canvas is then divided among the subplots (plus margins), so each axes’ drawable area scales with those numbers. I often do the math mentally when I want a specific pixel size for a web thumbnail or a poster panel.

Where it gets juicy is how text, line widths, and rasterization behave. Font sizes are typically in points (1 point = 1/72 inch), so their physical size on the figure stays consistent with figsize and dpi; bumping dpi increases pixel density, making text and lines crisper without changing their physical inch size. But saving is another twist: plt.savefig has its own dpi argument that overrides fig.dpi — handy if I make a quick onscreen 100 dpi fig but need a 300 dpi export for printing. Also, vector formats like 'pdf' or 'svg' don't rasterize curves at a given dpi, so they stay sharp when scaling; however embedded raster images or artists that are rasterized will still depend on dpi.

Practical tips I use: set figsize to control layout and spacing (how many subplots comfortably fit), use dpi to control resolution for output, and prefer vector formats for publication. If you're stacking many subplots, tweak figsize first, then adjust dpi if you need more pixel detail. I usually test with a small export at different dpi values until the labels and tick marks look right — it's almost satisfying, like fine-tuning a synth patch.

Short and sweet: figsize controls the inch-size of the whole figure; dpi scales inches into pixels. So a 4×3 inch figure at 200 dpi becomes 800×600 pixels. That total pixel area is shared by all subplots, margins, and labels, so add subplots? Increase figsize or dpi to keep things readable.

A few practical notes I use every time I plot: plt.savefig(..., dpi=...) overrides fig.dpi for saved raster outputs; vector formats ignore dpi for drawing primitives but embedded images still obey dpi; font sizes are in points (1 pt = 1/72 inch) so their physical size depends on figsize, not dpi. If labels look blurry on export, bump the save dpi or switch to 'pdf'/'svg' if possible.

I usually think in two steps — layout (figsize & subplot arrangement) first, then resolution (dpi or savefig dpi) second. That workflow prevents surprises, especially when preparing figures for slides or papers.