Skip to main content
Known Participant
November 13, 2016
Question

why does photoshop export 300 ppi image as 72 ppi?

  • November 13, 2016
  • 17 replies
  • 75628 views

why is it if i open an image in PS which has a dpi of 300 (image sourced from Shutterstock), work on the image and then use Export As JPG, the resulting ppi is 72 according to PS. I checked my Export Prefs and they are set to JPG and 100 for quality, so why does it export as 72 and not 300? I need to supply images in my document at 300dpi not 72dpi

17 replies

Legend
July 29, 2019

PPI data is saved in the TIFF metadata namespace. The pixels on disk do NOT change regardless of this setting.

If you save with a method that doesn't write that metadata, some programs default to 72ppi.

rob day
Community Expert
Community Expert
July 29, 2019

Here are the Save As formats that include the PPI resolution and print output dimensions:

Legend
July 29, 2019

ONLY if the tags are present in the proper namespace and if the viewer supports it.

This is like talking about color management. Lots of formats support color profiles, IF the creating program writes a profile tag and IF that is not deleted from metadata and IF the viewer also supports profiles.

Participant
June 15, 2018

Hi! You've posted this a long time ago, so I hope this helps you because I had the same problem.
Starting with a file set at 300 PPI with multiple layers I needed to export individually at 300 PPI. Using the Export/Layers to Files script gave me images at 72 PPI on JPG or PNG (so I could trim layers, otherwise all I needed were the JPGS). My work around this was to create a new file with the option for Artboards checked in, set to be 300 PPI. I dragged all the layers from the other file into the new one and individually converted each layer to an artboard. Each dartboard kept the size of each layer independently.

Then I went to File/Export?Artboards to files, chose the  Export content only option, unchecked the "include background option" and my files were perfectly exported at 300 PPI and at the dimension of each individual artboard (no white background included).
I tried it to export dartboards as PNG files and it still saved them all at 72.

I hope this helps you!

Participant
July 27, 2019

OMG I just read all of the posts and am worse off than when I started. I need to save 300 DPI files for an ETSY store to be downloaded for printing by the customer. They keep changing to 72 DPI. I "export as" and get it that I should use "save as" instead? So like the person who started the thread, I would like to understand why but think it might just cloud the issue more.

So is everyone SIMPLY  saying that all I have to do is SAVE AS instead of EXPORT as?

davescm
Community Expert
Community Expert
May 6, 2024

I'm sorry apparently i don't understand now...i sent to print a file that was 1181 x 2504px and i checked as always that it's 300ppi - then they told me that it is too big and I exported again (scaled 50%) and that worked. After i got blurry flyers printed out - i checked and everything that im exporting, thinking that its 300ppi - and it is 72. 
If i go on 'save as' - there is no option JPEG. 
Sorry if I'm writing a bit complicated - I'm just super confused now. 
Also i checked the photos that i exported like I always did and they are all 72ppi eventhough i set it up for 300...
Thanx for the help!


@Tijana368661393fub 1181 x 2504 pixels at 300ppi gives a print that is 3.93 x 8.34 inches on paper. Is that the physical size you were after?

 

If you used Export then the print will have no ppi value (the reason being that it is irrelevant for web images which is the primary use for Export). The 72ppi that you see is just what Photoshop re-inserts when opening an image with no ppi value in the metadata.

Dave

Legend
June 22, 2017

I didn't say resolution was irrekevant for JPEG and PNG. If these are to be printed or placed it's very relevant. What I said is that (1) it's irrelevant for web work and (2) export is for web work.

Either er if these statements might be wrong. (1) some people assert that ppi is important for web graphics. I've never understood the arguments here. (2) Some people might argue that the name of the Export function suggests it's for more general use. I have sympathy for that argument, but what do Adobe say?

ShipsAhoy
Participant
June 20, 2017

Hi Craig,

I understand and sympathize with your "Export As" frustrations and its inability to keep the original resolution. The workflow for our files requires creating a transparent PNG at 300 ppi (I'll explain why below.) We start with a native CMYK photoshop file at 100% size @ 300 ppi. The file gets reduced by 50% at 300 ppi. In previous versions of photoshop (CS4 or CS6?) "Export As" retained the original ppi. This made it perfect for our workflow, and everything could be done in one click. It reduced the file by half, changed it to PNG, changed it to RGB, retained transparency, and kept it at 300 ppi--all without having to make a single change to my native CMYK PSD. Unfortunately, newer versions of PS now change the resolution to 72 regardless of the original ppi. This adds a whole additional step when using "Export As" (changing the resolution back to 300 ppi) to the workflow, which is frustrating.

Other commenters have suggested simply using "Save As" but in my case, a 50% reduction still needs to be done, as well as converting to RGB before I can save it as a PNG. So this adds two additional steps to my process, plus it means I have to make sure NOT to save changes to my original PSD file. So "Save As" is a worse option for my workflow. When we are talking about a large team using this workflow daily, adding any additional steps is never good. And even more frustrating since we used to be able to do this without an issue until Adobe made the default resolution 72 ppi upon export.

For those that are suggesting that resolution doesn't matter because it's screen--you're right as long as it's being ONLY used on screen. For our workflow, the PNG files go on to a digital asset management library which is also the back end for our website. So resolution doesn't matter there.  However, these same PNG files also get used for print. Yes, that might sound heretical to some of you, but an RGB lossles PNG can be used just fine in certain print processes. Every once in a while we do get a bit of a color shift from the original CMYK PSD on certain images, but it's a sacrifice we easily made in order to reduce the number of files and amount of time to have and manage 2 different file types. When you're dealing with hundreds of thousands of files like this, a little color shift is perfectly acceptable for images that are merely product representations anyway--especially when it means not having to double our time and number of assets to accommodate both web and print scenarios. Since the DAM software requires a transparent PNG as the "original" source file in order to serve as the back end for the website, we are stuck with using transparent PNGs in our workflow for both web and print--and it has worked nearly perfectly (except for the "Export As" hiccup.)

I get that "Export As" is designed with web only use in mind, but it could be a much more powerful tool if resolution could be controlled, and maybe even some additional file types added. The workflow I've described maybe isn't typical, but for some of the reasons I've touched on it's the workflow we have to use. "Export As" used to meet our needs perfectly, but no longer does now that it changes the default resolution to 72.

For now, the best workaround is to change the resolution back to 300 ppi after export. I've considered using the "Generate Assets" feature, but it's a bit overkill with only one export happening per file. We do use that for some of our files where we have to generate many assets at 50% from one layered PSD. I've also considered setting up an action, but from a procedural perspective, I'd prefer our staff not have to rely on actions if they can accomplish it through simple menu commands (which used to be the case before Adobe changed the default to 72 ppi.) One additional step might not sound like a big deal to some people, but for those who work with large teams and workflows with many steps, one additional step makes a big difference.

Appreciate all of the ideas. But for now, the only answer to the OP is what Barb said: "while the dialog box should have a way to set the ppi, it doesn't." We all have different workflow requirements, and this would be a lifesaver for our team if it kept the original resolution instead of changing it (after all, if it's for web it doesn't matter, right?!) or if there was an option to set the ppi. I'll keep exploring the best workaround for our team.

Legend
June 21, 2017

I see the statement over and over that Export changes the resolution to 72 ppi. I don't think it does that, though the effect may seem to be. If I am right, these Q&A explain why it's wrong (but largely unimportant) to say that Export changes the resolution to 72 ppi.

Q. Do JPEG files have to contain a resolution (ppi value)

A. No, it's optional.

Q. What happens when an app opens a JPEG without a resolution (ppi)?

A. It's entirely up to the app what it does. Some apps will remember that there is no resolution at all, or ask for one. But most apps will set a default resolution.

Q. Ok, what happens when Photoshop opens a JPEG without a resolution (ppi)?

A. Photoshop assumes 72 ppi, and you cannot tell whether this came from the file or was used because the file said nothing. Many other apps do exactly the same thing.

Q. So, does Export set 72 ppi?

A. No, export sets NOTHING because it is for use with web graphics, where resolution (ppi) is irrelevant.

Q. How does that go again?

A. The export sets NO RESOLUTION (ppi). When an app reopens the JPEG, Photoshop (and many others apps) assume it was 72 ppi. So it's exactly as if the resolution was set to 72 ppi and impossible to tell without a detailed analysis of the JPEG internals.

ShipsAhoy
Participant
June 22, 2017

Thanks for sharing this, TSN, it's an interesting thought. As you know, resolution does have meaning for print, and while the resolution may seem irrelevant since the pixel count doesn't change, it does change the size that the image prints. What I find strange--especially given your proposed explanation of how "Export As" supposedly treats resolution--is that it's different than the behavior of "Save As" which allows users to set the resolution--which in turn sets the image dimensions.

Because PS allows all kinds of file types to be saved out from the "Save As" dialog box, it makes sense that resolution would just be a parameter for all of them regardless of whether it's relevant or not to the specific file type. And if you hold to the idea that resolution is irrelevant for png and jpg, then being able to set it in the "Save As" dialog box is extraneous, and being able to set it in the "Export As" dialog box seems unneeded.

I hold a different perspective, which is that resolution--and by extension the corresponding image width and height--has great relevance in certain situations for png and jpg. Maybe it's not your situation nor is it a common situation, but nonetheless it is the situation I'm in and have no choice but to work with. Based on the fact that many people seem to be asking this question, I would guess the OP and I are not the only ones who see a use for the function.

I'm also pointing out that this behavior for "Export As" (whether warranted or unwarranted) was not always like this, and previous versions of Photoshop DID retain the starting resolution for jpg and png. It no longer does, and for most people that might be insignificant. For me, it's significant and I'd love to have an option to set the resolution on export. Since noticing the change after upgrading and the consequences on my workflow that I didn't have before, I've been wondering the same thing that the OP was asking. Your explanation makes sense (even though I disagree with the premise that resolution is irrelevant for jpg and png.) Unfortunately, it doesn't solve my particular issue.  But it's helpful to understand the behavior and the apparent thinking behind the behavior.

Thanks for considering the question and sharing your knowledge. It's great to be able to discuss such nerdy details like this!

Barb Binder
Community Expert
Community Expert
November 14, 2016

I need to supply images in my document at 300dpi not 72dpi

And you need to supply them as JPG? You can't supply native PSD files?

~Barb at Rocky Mountain Training
Known Participant
November 14, 2016

yes, in theory the images could be supplied as native PSD files, but in my case the images need to be 300ppi used within an InDesign document as a whole. And I dont see that i should have to use native PSD's for every image i use in an InDesign document destined for professional print.

Derek Cross
Community Expert
Community Expert
November 14, 2016

The advantage of using native PSD files in InDesign is that you can round-trip to adjust them.

By the way, I assume you know that you supply a PDF to your (commercial) printer from InDesign, probably PDF/X-4.

Silkrooster
Legend
November 13, 2016

To add to Derek's response, save as allows you to specify the ppi, whereas save for web assumes it will be on a screen where ppi is irrelevant.

Known Participant
November 14, 2016

Hi Silkrooster, thx for the added comment, but my question is related to why when using "export as" for an image that is 300ppi, PS seems to export and save it as a 72ppi resolution image by default?

Derek Cross
Community Expert
Community Expert
November 14, 2016

Use Save As, not Export As.

Derek Cross
Community Expert
Community Expert
November 13, 2016

Don't use Save for Web, use Save As, and select JPG from the Format drop down menu.

Known Participant
November 14, 2016

Thanks for advice Derek, but I am not using save for web or save as, but my question relates to the "export as" function.