unDraw Essentials

How to Organize Your Downloaded unDraw Illustration Files

A practical system to organize unDraw illustration files: folder structure, file naming, keeping SVG originals beside PNG exports, color variants and a simple license note.

A tidy folder tree on a screen with illustration files renamed in a clear pattern and sorted into project folders

Illustration collections do not become messy all at once. They become messy one download at a time: a file left in the downloads folder, a second copy saved under a slightly different name, a PNG separated from the SVG it came from, until a project holds forty files and nobody can say which one is the original, which color it carries, or where it was used. This guide gives you a complete, lightweight system to organize unDraw illustration files from the first download onward: a folder structure that mirrors how you work, a naming pattern that answers questions at a glance, a rule that keeps editable originals beside their exports, and a short license note that records the terms you rely on.

The system takes about ten minutes to set up and seconds to follow per download. It scales from a solo blogger with twelve files to a team shipping client work every week.

Why downloaded illustrations get messy so fast

Three habits cause almost all of the chaos. The first is downloading without renaming. Browser downloads arrive with the site's own file names, and repeated downloads pile up as near duplicates with numbers appended. A month later, three files claim to be the same scene and none of them can be trusted. The second habit is separating formats. The SVG goes into the project, the PNG into a presentation folder, a recolored variant onto the desktop, and the relationship between them evaporates. The third is working from copies of copies: editing a file that was itself an edit, so no clean starting point survives.

Each habit is understandable in the moment and expensive later. The fixes are correspondingly simple: name files when they arrive, keep each scene's files together, and protect one untouched original per scene. The sections below turn those fixes into a concrete structure.

A folder structure that mirrors your projects

Organize by project first, because that is how you will search. Inside each project, keep one illustrations folder with two subfolders: originals and exports. The structure looks like this:

Projects/
  Client Website Redesign/
    illustrations/
      originals/
      exports/
  Product Launch Deck/
    illustrations/
      originals/
      exports/
  Shared Library/
    originals/
    exports/

The originals folder holds the files exactly as they were downloaded, untouched, forever. The exports folder holds everything derived: resized PNGs, recolored variants, cropped versions for specific placements. If an export is ever lost or a design changes, it can be regenerated from the original in minutes.

The shared library folder is optional and suits people who reuse favorite scenes across projects. Keep only true general purpose scenes there, and copy files into projects rather than linking to them, so a project folder always contains everything it needs. For a personal site or a single ongoing project, one illustrations folder with the same two subfolders is enough; the discipline matters more than the depth.

A file naming pattern that answers questions

A good file name answers three questions without opening the file: what scene is it, what variant is it, and what role does it play. Use this pattern:

scene-name_variant_role.format

PartRuleExample
Scene nameShort descriptive words in lowercase, joined with hyphens, based on what the scene showsteam-onboarding, empty-inbox, payment-success
VariantThe accent color name or hex, or the edit that defines this versionpurple-6835da, teal, dark-bg
Rolemaster for the untouched original, or the placement for an exportmaster, hero, email-header
FormatThe real file extension, never renamed by hand.svg, .png

Applied consistently, a folder listing reads like documentation: payment-success_purple-6835da_master.svg is obviously the untouched original, and payment-success_purple-6835da_hero.png is obviously its export for the hero placement. Compare that with download(3).svg and final-final2.png, which answer nothing. Two more rules keep names useful: avoid spaces, which break in some tools and URLs, and never rename the file extension, since a PNG renamed to .svg is still a PNG and will confuse every tool that trusts the name.

Keep the SVG original beside its PNG exports

The most valuable relationship in your library is between a scene's SVG master and the PNGs exported from it. The SVG is the only version that can be resized without loss and recolored without repainting, as our unDraw SVG vs PNG comparison explains. The PNGs are disposable renderings of it. Keep them in the same project, under names that share the scene prefix, so sorting the folder alphabetically groups a scene's whole family together.

This pairing pays off in the three situations that recur in every project. A rebrand changes the accent color: recolor the masters and re export, following the workflow in our guide on how to change an unDraw illustration color. A layout grows: export a larger PNG from the master instead of stretching the small one. A stakeholder asks what changed: compare the export against the untouched master and answer precisely. None of these are possible when the only surviving file is a flattened PNG of unknown origin.

One protection rule deserves emphasis. Set your originals folder, or at least the master files, apart from daily editing. Some teams mark masters read only at the file level; others simply adopt the rule that editors open copies. Either way, the master is never the file open in the editor when someone presses save.

Add a short license note to the library

Inside the illustrations folder, keep one small text file, license-note.txt, recording where the artwork came from and the terms in force when you downloaded it. Five lines are enough: the source site, the license page address, the date you downloaded the core set, and a one line summary of what you rely on, such as free commercial use without attribution, with no redistribution of the assets themselves.

This note exists because questions arrive late. A client asks, a year into a project, whether the illustrations can stay in the product. A teammate wonders whether a scene can be added to a shared asset bundle, which the license does not allow. The note, backed by our plain language walkthrough of the unDraw license, answers in seconds and records that the use was considered rather than assumed. Update the date line when you download a new batch; keep old notes if terms matter to an old release.

The per download routine, in under a minute

  1. Download deliberately. Set the color first, choose the format, and save, as covered in our guide on how to download unDraw illustrations.
  2. Move the file immediately from the downloads folder into the project's originals folder.
  3. Rename it on arrival using the pattern: scene, variant, master.
  4. Take the second format too when there is any chance of needing it, and file it under the matching name.
  5. Export into the exports folder when a placement needs a derived file, named with its role.
  6. Note anything unusual in the license note or a project readme: a special edit, a trademark visible in the scene, a placement to revisit.

Six steps, most of them seconds long. The routine feels like overhead exactly once, the first time. After that it is simply how files arrive, and the library quietly stays clean.

Make the routine stick

Systems fail when they depend on remembering, so remove the memory from the routine. Create the project folder structure at the moment a project starts, before the first download tempts you to improvise. Keep the naming pattern written in a note at the top of the illustrations folder, where future you and every collaborator will see it at the exact moment it is needed. If you download illustrations often, set your browser's download location to a single inbox folder and process it at the end of each work session, the way you would clear an email inbox: move, rename, file, done. Five minutes of processing beats the alternative, which everyone in design work has lived: a downloads folder holding three hundred files, a deadline tomorrow, and the one illustration you need hiding under a name like final(2).svg. The routine is not really about tidiness. It is about making the right file findable at the moment of need, every time, without heroics.

Cleaning up an existing messy collection

If you are starting from chaos rather than from zero, do not attempt a grand reorganization in one sitting. Work in passes. First, gather every illustration file into one staging folder so the true size of the collection is visible. Second, delete exact duplicates, keeping the copy with the clearest name. Third, identify masters: for each scene, the largest, cleanest SVG is almost always the closest thing to an original; protect it and treat everything else as an export. Fourth, rename in place using the pattern, scene by scene, starting with the scenes currently live in your project. Fifth, move the renamed families into the project structure.

Scenes you cannot identify or no longer use can be archived into a single folder rather than deleted, at least until the current project ships. And when memory fails about where a scene came from or which color it carries, the reliable fix is a fresh download: our guide on how to find unDraw illustrations will help you relocate the scene on the site, and a clean new master beats a doubtful old file every time.

The system on one page

  • One illustrations folder per project, with originals and exports subfolders.
  • Masters are downloaded files, untouched, never edited in place.
  • Names follow scene_variant_role, lowercase, hyphenated, no spaces.
  • SVG masters and their PNG exports share a name prefix and stay together.
  • A five line license note records the source and terms.
  • Every download gets moved, renamed and filed within a minute of arriving.

That is the whole method. It asks for a minute of discipline per file and returns hours of searching, re downloading and second guessing across the life of a project.

Protect the library with backups and sensible storage

An organized library is worth protecting, because its value is not the files themselves but their exact state: the right color, the clean master, the variant that matches the live page. Keep the illustrations folder inside storage that is already backed up, whether that is your synced cloud folder, your project's repository or your team's shared drive. For website projects, committing the SVG masters alongside the site code is a particularly good fit: the artwork versions travel with the pages that use them, and a change to an illustration shows up in the project history like any other change.

What does not work is a library that lives only on one laptop's desktop, or only inside a chat thread where files were shared. If the machine is replaced, the project loses its masters and keeps only whatever flattened copies were published. Published copies can be re downloaded from a live page in a pinch, but they are exports, at export sizes, and the clean originals behind them are gone. Ten seconds of filing into backed up storage, at download time, removes the whole category of risk.

Keep a simple index of what is used where

For projects with more than a handful of scenes, add one small index file, a plain text or spreadsheet list with three columns: the scene's file name, where it is used, and anything special about it. An entry might read: payment-success master, checkout confirmation page and success email, recolored variant exists for the dark theme. The index takes a line per illustration and pays for itself the first time someone asks whether a scene can be changed, which pages a rebrand must touch, or whether a particular illustration is already spoken for elsewhere in the product.

Teams benefit most. One person maintains the library and the index, downloads go through the routine instead of around it, and reviews check new artwork against the naming pattern before it merges. None of this needs software or ceremony. It needs the agreement that the library is shared infrastructure, treated with the same care as the codebase or the brand files, because in every way that matters to the finished project, it is.

Sources and further reading