<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Scientific Figure]]></title><description><![CDATA[Scientific Figure]]></description><link>https://scientificfigure.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Thu, 12 Nov 2026 09:14:21 GMT</lastBuildDate><atom:link href="https://scientificfigure.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why Your Journal Figure Looks Wrong at Single-Column Size]]></title><description><![CDATA[What Elsevier, Nature and PLOS actually specify for figure width and resolution, why 300 dpi depends on print size, and a one-minute check before you…]]></description><link>https://scientificfigure.hashnode.dev/why-your-journal-figure-looks-wrong-at-single-column-size</link><guid isPermaLink="true">https://scientificfigure.hashnode.dev/why-your-journal-figure-looks-wrong-at-single-column-size</guid><category><![CDATA[Science ]]></category><category><![CDATA[data visualization]]></category><category><![CDATA[research]]></category><dc:creator><![CDATA[Scientific Figure Team]]></dc:creator><pubDate>Fri, 06 Nov 2026 10:05:34 GMT</pubDate><content:encoded><![CDATA[<p>Most figures that look bad in print looked fine on the screen they were made on. The usual cause is not the data or the software. The figure was drawn at the wrong size, and everything else followed from that.</p>
<p>Here is what the publishers actually write down, and the one habit that avoids most of the trouble.</p>
<h2>Start from the column width</h2>
<p>The first number to fix is the width the figure will be printed at. Type size, line weight and resolution are all stated at final size, so they only mean something once you know what final size is.</p>
<table>
<thead>
<tr>
<th>Publisher</th>
<th>Single column</th>
<th>Double column</th>
</tr>
</thead>
<tbody><tr>
<td>Elsevier</td>
<td>90 mm</td>
<td>190 mm</td>
</tr>
<tr>
<td>Nature</td>
<td>89 mm</td>
<td>183 mm</td>
</tr>
<tr>
<td>PLOS</td>
<td>Minimum 6.68 cm</td>
<td>Maximum 19.05 cm</td>
</tr>
</tbody></table>
<p>The failure looks like this: you draw at whatever width your software opened with, and the journal scales it down at layout. Reduction shrinks the lettering and the strokes along with the artwork. A chart drawn at 190 mm and reduced to 90 mm takes 7 pt axis labels down to 3.3 pt, which is below every stated minimum.</p>
<h2>What 300 dpi really means</h2>
<p>Resolution is only defined at a physical size. Elsevier states it as an equation: pixels equal dpi multiplied by print size in inches.</p>
<p>A 90 mm figure at 300 dpi is 1063 pixels wide. The same 1063-pixel file placed at 190 mm is a 142 dpi figure, and no setting in any application changes that.</p>
<p>The targets differ because they describe different content:</p>
<ul>
<li><strong>Elsevier:</strong> 300 dpi for halftones, 500 dpi for combination art, 1000 dpi for line art</li>
<li><strong>PLOS:</strong> 300 to 600 dpi, with files capped at 10 MB</li>
<li><strong>Nature:</strong> at least 300 dpi at the maximum size the image will be used</li>
</ul>
<p>Line art gets the highest number because a hard black edge on white is where sampling artefacts show most.</p>
<h2>Raising the dpi afterwards does nothing</h2>
<p>Nature warns about this directly, and it is one of the most common mistakes. Increasing an image's resolution in an artwork program does not add detail. If the file was too small, go back to the source and export it again at the right size.</p>
<h2>The check that takes a minute</h2>
<p>Nature's advice predates modern software, and it still works. Look at the figure at the smallest size it might be printed, and confirm the lettering is readable and the lines are heavy enough.</p>
<p>The modern version is to place the artwork in a document at exactly 89 or 90 mm, print it on paper, and look at it. Screens flatter figures. Paper does not.</p>
<p>Where the publishers disagree, follow the document for your target journal. We keep the wider version, including vector versus raster, type sizes and colour, in our guide on <a href="https://scientificfigure.com/blog/how-to-make-scientific-figures">how to make scientific figures</a>.</p>
<hr />
<p><em>From the team behind Scientific Figure, an AI figure generator for researchers. Publisher rules change, so check the journal's own page before you submit. Drafted with AI assistance and checked against our sourced guide.</em></p>
]]></content:encoded></item></channel></rss>