PNG graph.save(t=png,d=300) exports at ~96 DPI metadata, not 300 DPI
Posted: Tue May 19, 2026 9:45 am
Hi EViews team,
I think there may be a bug in PNG export DPI metadata.
I exported graphs with commands like:
The program runs successfully and the PNG files are created, but the resulting files do not appear to be tagged as 300 DPI. Both files are 96 DPI.
The pixel dimensions are large enough, so d=300 may be affecting export sizing, but the PNG resolution metadata/pHYs chunk is still written as ~96 DPI. This causes automated checks and downstream publishing workflows that inspect DPI metadata to fail.
Expected behavior: save(t=png,d=300) should produce a PNG whose horizontal and vertical DPI metadata are 300.
Can you confirm whether d=300 is intended to set PNG DPI metadata, and if so whether this is a known issue?
Thanks.
I think there may be a bug in PNG export DPI metadata.
I exported graphs with commands like:
Code: Select all
rer_trends.save(t=png,d=300) "RER_trends.png"
rer_irf.save(t=png,d=300,w=8,h=5) "RER_IRF.png"
The pixel dimensions are large enough, so d=300 may be affecting export sizing, but the PNG resolution metadata/pHYs chunk is still written as ~96 DPI. This causes automated checks and downstream publishing workflows that inspect DPI metadata to fail.
Expected behavior: save(t=png,d=300) should produce a PNG whose horizontal and vertical DPI metadata are 300.
Can you confirm whether d=300 is intended to set PNG DPI metadata, and if so whether this is a known issue?
Thanks.