I work as a photographer but recently I've been working on stretching my skills and took on a project to create a graphic design for a non-profit. The designs are complete and the organization was satisfied with the work.

I'm in the process of creating the final package and am including the images in PNG format. It seems to me like this might be the best option considering the multiple ways in which the logo might be used (on print, web etc.). Just looking for some guidance on the formats typically used for delivery. Are there any situations in which you deliver the original PSD files (assuming you're using photoshop)?



2 Answers 2


There is no one correct answer here. Each project needs to be evaluated and deliverables should be discussed with the client PRIOR to any work being started.

In general.....

  • Print projects consisting of brochures, business cards, books, manuals, sales pieces, etc. generally require only a PDF deliverable. The native files used in construction the project are retained by the designer. There are some cases where the native files are desired by the client. This, again, should all be worked out prior to work starting and prior to any quotes being given.

  • Web projects consisting of web sites, banners, etc, generally require HTML/CSS text files in many cases. There are times when a client wants layered Photoshop files. And sometimes the client merely wants png files. There's no one answer here.

  • Logotypes/branding - Logos should always be delivered in a vector format in addition to any formats such as png or jpg.

Each project will have it's own needs and tool requirements so its difficult to give a single answer to your question.

I have no problem delivering a layered PSD file for a web page if that's what the client wants. Of course, I need to know this is what they want from the start because I don't design web sites with only Photoshop. I'll code pages and build images to drop into the code. It's exceptionally rare for me to build an entire page with Photoshop. It's just faster and more accurate to build code. I may prototype or sketch with Photoshop but that's generally as far as I go with that tool. I've run into too many cases where I here "The text in the design we approved doesn't match the text on the web site." And trying to explain the difference between image text and live HTML text can be impossible with some clients.

For print work I pretty much never release native files whether they are Photoshop, Illustrator, or Indesign files. Deliverables are customarily only a PDF. If the client wants the native files, I'll provide them for a fee. They are never free of charge.

For branding/logos I provide a native vector format, then additional formats as I see fit. This means you can't merely use Photoshop and be done. You should use Illustrator, CorelDraw, Freehand, Xara,... some vector application. Photoshop, while a great tool, never creates true vector files. Generally a logo delivery consists of .ai, .eps (vector), .pdf, .psd, .png, and .jpg. I also provide color breaks for each format. So that means an RGB .ai files, a CMYK .ai file, a Spot color .ai file, and so on. any raster-based files beyond a PSD are provided for client convenience. The .png or .jpg or even .gif are merely provided because clients expect to see those format because they are familiar with them. These formats also provide immediate use for many of the clients own needs (throw it on their facebook page, etc).

  • Thanks very much for the detailed explanation. There's a bunch of stuff that I'll need to look into but thanks for the great starting point.
    – dinesh
    Commented Nov 5, 2012 at 0:42

As a rule of thumb, designers retain the original format files such as the actual photoshop, illustrator or indesign files. The client gets the resulting jpg, eps, PDF, etc. This protects your work and your future as a designer.

I've seen it happen where designers turn over their original format files, and the client then turns around and hires an inferior designer (like thru outsourcing) for pennies on the dollar for future projects.

I believe the more important issue here is to make the communication for the end goals and requirements a top priority during a preliminary meeting with the client. If they want the original format files, it needs to be in the contract. And then charge a lot more for including them. Also reserve your copyright to your designs, and if the client wants the copyright, charge more for that too.

For a comparison, consider a custom motorcycle builder. A client wants a really awesome bike. The builder prototypes, designs, and assembles it. At the end, the client gets the bike. But by providing the client with the original format file, its similar to giving the client all of your tools you used to build the bike in addition to the bike itself. Now the client doesn't need your services anymore.

If the client insists they need the original format for X, Y or Z reasons, almost all the time a flattened format will work just as fine. If they still insist on the original file, then insist it's a standard contract that the original format file comes with a much higher price.

And if you need contract examples, check out http://docracy.com or reference the AIGA standard form of agreement at http://www.aiga.org/standard-agreement/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.