<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Magalog Guy&#039;s MagaBlog &#187; Photoshop</title>
	<atom:link href="http://magalogguy.com/blog/tag/photoshop/feed/" rel="self" type="application/rss+xml" />
	<link>http://magalogguy.com/blog</link>
	<description>Direct Marketing Design That Boosts Sales Performance - Magalogs, Sales Letters, Books, &#38; More</description>
	<lastBuildDate>Wed, 02 May 2012 21:27:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why you should request your designer&#8217;s source files</title>
		<link>http://magalogguy.com/blog/2009/12/13/why-you-should-request-your-designers-source-files/</link>
		<comments>http://magalogguy.com/blog/2009/12/13/why-you-should-request-your-designers-source-files/#comments</comments>
		<pubDate>Sun, 13 Dec 2009 15:57:26 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[magalogguy]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[brochure]]></category>
		<category><![CDATA[Illustrator]]></category>
		<category><![CDATA[InDesign]]></category>
		<category><![CDATA[logo]]></category>
		<category><![CDATA[magalog]]></category>
		<category><![CDATA[native files]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[Photoshop]]></category>
		<category><![CDATA[QuarkXPress]]></category>
		<category><![CDATA[sales letter]]></category>
		<category><![CDATA[source files]]></category>

		<guid isPermaLink="false">http://magalogguy.com/blog/?p=232</guid>
		<description><![CDATA[On the surface, this may seem like a boring topic. But I urge you to take the time to read this and understand the issue as well as the consequences of not caring. For any type of layout project &#8211; &#8230; <a href="http://magalogguy.com/blog/2009/12/13/why-you-should-request-your-designers-source-files/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>On the surface, this may seem like a boring topic. But I urge you to take the time to read this and understand the issue as well as the consequences of not caring.</p>
<p>For any type of layout project &#8211; magalog, sales letter, book, brochure, etc. &#8211; your designer likely is using some professional-level design tool like InDesign, QuarkXPress, Photoshop or Illustrator.</p>
<p>When he/she sends you a proof, it&#8217;s usually a PDF that&#8217;s easily viewed on just about any computer. Sending you the actual source (or native) files from those professional level tools would be pointless if you didn&#8217;t have that software yourself. You wouldn&#8217;t be able to easily open the files, if at all. And most projects are made up of many source files.</p>
<p>That&#8217;s why PDFs are so great&#8230; one file to see the completed project. That makes your life easy.</p>
<p>Print shops sometimes want to print your project from source files. Other times they&#8217;re just as happy with a press-quality PDF. It depends on the printer and the project. Designers are happy to provide the printer with source files if required. (If they&#8217;re not, they&#8217;re not doing you any favors. Consider finding another designer.)</p>
<p>But quite a number of designers will do just about anything not to hand over source files to the client. This is a very controversial subject and I don&#8217;t make many friends in the design community when I discuss it because I&#8217;m very pro-client on this.</p>
<h3>Why some designers don&#8217;t want to give you source files</h3>
<p>Some designers are afraid that if you have the source files, you&#8217;ll simply do future projects yourself, or hand over those files to someone who will work cheaper. By having the source files, it may save another designer lots of time creating similar projects. Personally, I don&#8217;t want clients to feel they have to work with me. If a client doesn&#8217;t see any of the extra value I bring to a project, we&#8217;re probably not a good long-term fit anyway. So if it&#8217;s just a single project and they&#8217;re going to use that as template for years to come without using me, so be it.</p>
<p>Other designers fear that the client will muck up the files and create a mess that either makes the end-result look bad (with the blame being unfairly placed on the designer), or cause the designer extra work to fix the mess. To be honest, that&#8217;s a valid point; I&#8217;ve seen it happen. My personal method of dealing with that is to be clear what the results may be if the client does alter files. If they insist on tampering with the files and causing me extra headaches, I simply stop working with them. (I value my sanity.)</p>
<p>And then there are designers who are happy to hand over the source files&#8230; for a price. That&#8217;s not something I do &#8211; I give them to the client for free if they want them &#8211; but charging extra for source files is very common in the industry. It&#8217;s a discussion to have with your designer before the project starts and have that included in your agreement.</p>
<h3>How I came to my &#8220;You can have the source files&#8221; policy and why you should care</h3>
<p>Unfortunately, &#8220;stuff&#8221; happens. Real life experiences opened my eyes to why clients should get their source files.</p>
<p>Let&#8217;s say you have a magalog that&#8217;s working great for you, but you change your company&#8217;s phone number, address or a URL. If you&#8217;re still working with the same designer who created the magalog, no problem.</p>
<p>But what happens if the designer went out of business and you can&#8217;t get in touch with him? (Freelancers going out of business is an unfortunate reality.)</p>
<p>What happens if you have a falling out with the designer and they refuse to talk to you or do anything to help you? (That happened to a client of mine with his previous designer.)</p>
<p>What happens if you&#8217;re unknowingly working with a designer who has a terrible back-up policy? Computers crash, files disappear. Happens all the time. I&#8217;d like to say that most freelancers are good about making regular back-ups. Experience tells me that not everyone does. How safe are your files with your designer?</p>
<p>What happens if you want to print more copies of the magalog with a new printer, but your designer is out-of-business (or not speaking to you) and you have nothing but a low-quality PDF proof?</p>
<p>Well, here&#8217;s what happens: A quick, inexpensive change turns into a brand new project for a new designer. That costs you, the company, more money and takes extra time.</p>
<p>It didn&#8217;t have to come to that if you had the source files to hand over to someone else. Or could hand them back to your original designer if something bad happened on his end.</p>
<h3>The argument that should cause you to consider finding a new designer</h3>
<p>If a designer ever gives you the old &#8220;Well, does a restaurant give you the recipes for meals on their menu?&#8221; argument for not handing over source files, kindly remind them they&#8217;re not a restaurant. But if that&#8217;s how they want to be judged, ask them if you&#8217;ll get &#8220;free refills&#8221; on certain design services or get &#8220;Happy Hour&#8221; pricing.</p>
<p>It&#8217;s a silly argument and any designer that uses it on you should be embarrassed. Consider whether you want a long-term relationship with a designer like that.</p>
<h3>Here are some things a designer may not be able to hand over</h3>
<p>1. Fonts &#8211; Most fonts have copyright restrictions of some kind. It&#8217;s usually OK for the actual fonts to be packaged and sent to the printer for printing along with the source files. But sending you, the client, the fonts with the source files can be a legal no-no. Your options are to simply take the source files without the fonts, or get a list of the fonts used by your designer and buy them yourself.</p>
<p>2. Unique creations &#8211; For this article, my focus is really on copy layout projects. I am, however, sensitive to designers who create logos or other unique pieces of art. But designers can &#8220;flatten&#8221; an image so that you can still have the source file, but are prevented from editing the pieces that make up the final result.</p>
<p>A logo is a good example. You may need to give that logo file to another designer for a different project. Having the flattened source file allows that designer the maximum flexibility to add the logo to a letterhead, banner, business card, or some other project that the logo designer doesn&#8217;t handle. Most logo designers understand that and will provide you with the appropriate file(s).</p>
<p>3. Plug-ins &#8211; Plug-ins are software extensions that designers can add to their design tools to help automate tasks or create some unique design element. It&#8217;s likely that the plug-in has copyright restrictions that prevent the designer from handing it over to someone else. That might mean that while you have the source files, you can&#8217;t edit some portion of the project, or even open it, because you don&#8217;t have the plug-in. That&#8217;s another case where you may need to buy the same plug-in assuming you have the same design tool your designer is using.</p>
<p>There may be other valid reasons, but I simply want to make you aware of some common situations where it truly is an issue.</p>
<p>Beyond that, it&#8217;s always in your best interest to get source files and store them in a safe place on a company server or back-up DVD.</p>
<p>Boring, I know, but essential.</p>
]]></content:encoded>
			<wfw:commentRss>http://magalogguy.com/blog/2009/12/13/why-you-should-request-your-designers-source-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

