Speeding up icon exports with Photoshop action scripts

Working through dozens of icon files by hand can drain an entire afternoon, and that's the kind of slow grind that pulls Australian designers away from the creative work they enjoy. Whether you're freelancing from a Brisbane home studio or shipping assets for a Sydney-based agency, automating your export workflow gives you back hours each week. Photoshop Actions offer a powerful way to standardise output, enforce naming conventions, and push every layer through the same finishing pipeline with a single click.

The same logic applies whether you're preparing assets for a native app, a slide deck for a Melbourne client, or a Figma handoff for a Perth startup. Once you understand how Actions record your moves, you can replay them across entire folders in seconds. The result is a consistent, repeatable process that survives deadline pressure and a busy arvo alike.

For designers grabbing layered PSDs from marketplaces like PSD Icons, the goal is usually to customise a few colours or sizes and push everything out as transparent PNGs. Doing that manually is tedious, but a well-built Action turns the whole sequence into a one-button operation.

Setting up your workspace for batch exports

Before recording, take ten minutes to organise your files. Drop the source PSD into a dedicated folder on your desktop, then create an Export subfolder using a clear pattern like client-name_icon-size_state. Many Sydney studios structure folders to mirror the delivery contract, so the directory itself becomes part of the handover. Keep your layers panel tidy by deleting hidden layers and grouping elements you won't touch.

It's also worth calibrating Photoshop's preferences. Set the export colour profile to sRGB, switch ruler units to pixels, and confirm the document is RGB rather than CMYK, since icon assets almost never need print colour space. These small adjustments prevent mismatches that ruin a batch later on.

Close any panels you don't need and dock the ones you do. A clean interface reduces the chance of clicking the wrong tool mid-recording, an error that will replay on every subsequent file.

Recording a reliable export action

Open the Actions panel via Window > Actions and create a new set like "Icon Export 2024". Hit record and walk through your ideal output process. Flatten optional layers, duplicate the visible composition, then run File > Export > Export As to lock in your resolution. Most designers building retina-ready assets choose 2x and 3x sizes, so record a sequence that creates both variants in one pass.

Naming matters. Use the batch rename function inside the export dialog, or pre-set layer names to match the desired output. If you're producing 24-pixel and 48-pixel variants, record the action with a placeholder name like "icon-set-AU" so you can swap it later. Build an Action flexible enough to handle a Brisbane client today and a Hobart agency tomorrow without rewriting.

Stop recording once the final export step completes, then test on a single icon. If the output matches your manual version, you're ready to scale up. Otherwise, undo, delete the action, and try again with fewer steps.

Applying the action to folders of icons

Once the action is reliable, head to File > Automate > Batch and point Photoshop at your source folder. Select your action set and the specific export action, then choose your destination folder. Set overwrite warnings to "Stop for Errors" rather than silently replacing files, which protects you from corruption when working through a large library. Designers in Melbourne's co-working spaces often run batches overnight, so logging errors to a file is a smart safety net.

You can also target multiple folders in sequence if your library is split by category. A fintech project might keep payment icons in one folder and navigation icons in another, both exported with the same action but saved into separate directories. This keeps the final delivery tidy for the developer who'll integrate them.

Remember that Actions operate on whatever is open, so close all stray files before the batch begins. One forgotten document can throw off your filename pattern and force a full rerun.

Managing naming conventions and folder outputs

A consistent naming convention saves hours during integration, especially when icons move from an Adelaide designer to a Perth developer. Use lowercase, hyphen-separated names with a clear structure: category-icon-variant-size. Names like "social-share-outline-24" read cleanly in code and survive translation between design tools without mangling.

If you export light and dark mode versions, bake the variant into the filename rather than relying on folder structure. Every file stays self-describing for anyone who downloads your pack later. Keep a simple spreadsheet mapping layer names to exported filenames, since Action-based batches silently skip anything that doesn't match your pattern.

For projects selling or distributing icons commercially, double-check the licensing terms attached to source files. The PSD Icons agreement spells out whether modifications and resales are permitted, keeping your work legally sound across AEST business hours.

Practical recommendations for a smoother pipeline

Once the technical setup feels comfortable, a few habits keep your pipeline reliable over time. The following list captures the small workflow tweaks that save the most time when running weekly exports for clients across different time zones.

• Record actions on a dummy file first, then run them on real assets once you've confirmed the output.
• Build separate actions for each common export size rather than parameterising a single one.
• Keep a text file in your export folder documenting each action's intended use, filename pattern, and last test date.
• Run a small batch of five to twenty icons before committing to a full library export.
• Store your action sets in a shared Dropbox or iCloud folder so your whole studio can use the same pipeline.

Time to put your new workflow into practice. Grab a free icon pack from PSD Icons, set up your export action in Photoshop, and watch a hundred files land in the right folders in under a minute. The first batch takes longer as you refine your steps, but every run after that pays back the setup time. Your future self, rushing a delivery before a Melbourne long weekend or a WA coastal break, will thank you for the head start.