Spring is upon us and we all know this means it’s time to do a lit­tle clean­ing. As you’re giv­ing your work­space a once-​​over con­sider this a per­fect oppor­tu­nity to clean up your not just around your com­puter but in it. Specif­i­cally, inside all those Pho­to­shop files packed full of rem­nants from ves­ti­gial ideas con­sid­ered and abandoned.  

Inher­it­ing a pre­vi­ous design­ers author­ing files at the start, or worse mid-​​way, on a project is usu­ally a night­mare which can waste hours by intro­duc­ing a learn­ing curve when what you really need and want to do is hit the ground running. For in-​​house design­ers try­ing to inter­pret the inten­tions of a col­lege, who is inevitably on vaca­tion and unreach­able, can lead to hours of frus­tra­tion. While file for­mat stan­dards abound there is no indus­try stan­dard or accepted prac­tices for work­flow. So, before you push author­ing files down­stream, or before archiv­ing, here are a few tips to make it eas­ier on the next guy—or future you.

Remem­ber, while this arti­cles focuses on Pho­to­shop, these tips can eas­ily be applied or adapted to Illus­tra­tor, InDe­sign or other author­ing programs.


The Prob­lem With Lay­ers: Nam­ing Defaults

Figure 1 Until Pho­to­shop adds mind read­ing as a fea­ture, we will be sad­dled by lay­ers with mun­dane default names such as Layer 1 copyLayer 1 copy 2 (Fig­ure 1), or hier­ar­chies of fold­ers titled Group 1Group 2, which do noth­ing to map files log­i­cally or con­vey your think­ing process on how you tackle the project. If your file con­sists of only a hand­ful of lay­ers than this is not so much a concern.

How­ever, if you file is com­posed of many layers—thirty, sixty, one-​​hundred or more—it can ren­der the file unnav­i­ga­ble and lead to hours of turn­ing lay­ers off then back on in a hunt-​​and-​​peck attempt to locate con­tent. It can get maddening.


Tak­ing Con­trol Of Your Layer Addiction

Figure 2 Pho­to­shop has tools built in to help you orga­nize your files. Apart from nam­ing lay­ers log­i­cally, you can group sim­i­lar lay­ers based on con­tent or loca­tion into a folder and assign the group a color (Fig­ure 2). Try com­bin­ing a folder hier­ar­chy with a stan­dard method of nam­ing lay­ers. Each layer is first iden­ti­fied by an abbre­vi­a­tion of the intended use, an under­score, then a descrip­tive name in camel nota­tion. As an exam­ple, if I have an RSS icon in my header, I might have a vio­let folder titled HEADER and in the folder a layer title icn_​rss or icn_​rssFeed.

Below are some other pre­fixes you may find use­ful:
icn  = an icon
img = any graphic ele­ment; vec­tor, raster, or CSS gen­er­ated.
btn  = a but­ton
txt   = any string of text; head­line, body copy, etc.
MASK = any shape  used as a mask­ing layer or clip­ping path.

Figure 3 This also makes it eas­ier to drill down through lay­ers with­out rely­ing on con­stant trips to the lay­ers palette. With the Move Tool selected right click (when using another tool use cmd (ctrl)+right click) and Pho­to­shop will present you with a con­text menu (Fig­ure 3) of all fold­ers and lay­ers under the cur­sors cur­rent posi­tion. If all your lay­ers fol­low a nam­ing con­ven­tion and are neatly nested inside fold­ers you eas­ily have direct access to exactly the con­tent you want.


Make A Note Of It

Unlike Illus­tra­tor or InDe­sign, Pho­to­shop does not allow you to set up a paste board or slug (you can fake a slug but it’s just beg­ging for trou­ble at pre­press) to leave notes for PA’s or Pre­press Oper­a­tors. When all other meth­ods fail to pro­vide you a way to com­mu­ni­cate your inten­tions, try the Note Tool—it’s located in the Eye Drop­per fly out menu or use cmd (ctrl)+I.


Delete Is Your Friend

As a design evolves over time it can become chalked full of  ves­ti­gial ideas. Lit­tle by lit­tle these exper­i­ments and tan­gents can eat up space—sometimes dou­bling the size of the file. But with your lay­ers organized


The Pay­off

Other than show­ing off your Pho­to­shop prowess there are tan­gi­ble ben­e­fits to a tidy author­ing file. The biggest ben­e­fit is smaller files which load faster, are more respon­sive when being edited, and occupy less stor­age space.

Case in point: I recently designed a web­site wherein the result­ing PSD weighed in at roughly 57MB. After the client approved the design, I cleaned up my lay­ers and comps and the result­ing file weighed in at 23Mb. This might not sound like a big deal con­sid­er­ing giga­bytes are now cheap as Chick­lets, but when you mul­ti­ply the sav­ings across hun­dreds or thou­sands of author­ing files this could trans­late to seri­ous cash being saved by slow­ing the ever-​​growing need to expand stor­age capac­ity. Not to men­tion less time spent wait­ing for files to trans­mit across networks.

If your on the design side of the equa­tion, clean­ing up your files means you leave noth­ing to inter­pre­ta­tion by a PA in another depart­ment, office, or even on the other side of the world. You also avoid the inro­duc­tion of mis­takes caused by acci­den­tal clicks turn­ing on a layer you never intended to have show up in the pub­lished piece. We’ve all seen an errant FPO rear it’s ugly head as we page through a publication.

As a PA, you can quickly and effi­ciently slice and dice design files into fin­ished pieces and negate time wasted wait­ing for replies from design­ers so they can con­vey how they intended a spe­cific design ele­ment be applied.

Do you have a method to your layer mad­ness? Share it with us below.

About the author

Jeff designs print and web expe­ri­ences for a vari­ety of clients and enjoys shar­ing what he learns along the way. He entered the indus­try at the split of web design from graphic design occurred and is now fas­ci­nated as the two dis­ci­plines are on the cusp of com­ing full cir­cle to merge into a new, media savvy gen­er­a­tion of design­ers. When not crazy busy, Jeff likes geo­caching and con­sum­ing copi­ous amounts of cof­fee. You should fol­low him on Twit­ter and Facebook.

OCD for PSD

1 Comments