Graphisoft · Archicad 28–29 Library
2D Library
Architects choose the drawing style first. The library asked for the species.
What
New 2D trees, people and animals for Archicad's object library, with a selection flow that starts from how architects actually work.
My part
Style-first selection for trees and people, the preview images, the 2D-only and migration decision, and all 804 graphics through an AI-assisted workflow.
Result
Shipped in Archicad 28 Library Update 1 and Archicad 29 Library Update 1.
first, pick a drawing style
01 — context
Graphics that make drawings readable
Archicad is Graphisoft's BIM software for architects. Its library includes 2D trees, people and animals that architects place in plans, sections and elevations to show scale and match each project's drawing style.
Across two library updates, I designed how users find and choose these objects, decided how they fit into the existing library, and drew every graphic.
02 — the problem
The dialog asked the wrong question first
Choosing a tree took four steps: search, pick a species group, pick the species from a dropdown, then find the drawing style in another dropdown in the tree settings. The previews didn't help: all styles were stacked on top of each other, so you couldn't tell what you would get.
Community forum threads showed why this hurt: architects first decide how a tree should look in the drawing (photorealistic, silhouette or symbolic), and only then the species. The dialog put that first decision at the very end.
People had a different problem: two libraries, the global one and one made for the German market, which we wanted to merge and extend. I audited both by placing every figure in every view. Almost all existed only in front view, top views were a single line, and the two used different drawing styles.
Volume
Hundreds of new graphics, each in three drawing styles, without losing consistency.
Two libraries
The German people library had to fit into the global one, not sit next to it.
A mature library
Users already had these objects in their projects. Nothing could break.
03 — trees
Fix the order, then the previews
Separate style from view
I split the old species groups into two clear dimensions: drawing style (silhouette, symbolic, photorealistic, called Texture for trees) and view (side, top). Users now pick the style first, then the tree. I proposed the side and top split, discussed it with the team and the other designers, and they agreed.


Tree selection before and after the redesign.
Previews that show what's inside
Each preview had to show the style and also signal that the group holds more trees. Equal-size thumbnails were too small to read. A folder metaphor said "there's more inside" but felt too busy. Overlapping trees brought back the old problem: they merged into one unreadable shape. The final version uses hierarchy instead. One large tree shows the style, and a column of small ones shows the variety. I dropped the folder icon too, because it added noise, not meaning.

Preview iterations: equal grid, folder metaphor, overlapping trees.
More control over how trees look
I added a contour line on/off switch and gradient fill settings to all silhouette and symbolic trees. Architects can match trees to each project's graphic style without editing the objects by hand.
04 — people
Style first, then what they're doing
Group by activity
The same logic for people: style first, then activity. Standing, Moving, Sitting and Reclining, Interacting, and Activities. I chose these groups from desk research (Revit and SketchUp content, visualization sites, architectural drawings) and by asking colleagues with architecture degrees. The figures face different directions, so every view has figures that work in it.
No top view
Top-view people are hard to read, and the old ones were just a line. Anyone who still needs one can use the existing 3D people. The team agreed.
Keep what worked in the German library
Its symbolic figures could be colored part by part: skin, hair, clothes, shoes. We carried this over to all new symbolic figures, so architects can match people to a project's color scheme.
05 — 2D only
Removing nothing that worked
The old objects combined 2D and 3D in one element. In 3D, an old bug showed them as empty billboards, and nobody had capacity to fix it. Architects mostly use these figures in sections and elevations anyway, so I proposed making the new objects 2D-only, with 2D and 3D as separate elements. This took nothing away: the 3D view was broken for everyone.
The harder question was what happens to objects already placed in users' projects. I mapped every case on a Miro board: how old 3D and 2D versions could migrate, and what users would see in each view.
The migration plan we didn't ship: three cases, each with its own exceptions. Mapping it out is what made the simpler option obvious.
Keep the old, add the new
Converting old objects meant more development work and more risk of breaking existing projects. I proposed a simpler approach: the old trees stay in the Garden folder, untouched. Copies of them go into a new Smart Greenery folder next to the new trees, with the same new contour and gradient controls, and non-tree items like parasols move to Park and Street. Nothing changes when users open an existing project.
One rule for what goes where
If the difference between two objects is visible in the preview image, they are separate objects. If it isn't, they are options of the same object. The team agreed.
06 — workflow
804 graphics, one designer
I made all 804 graphics myself, so I set up a workflow that could handle the volume.
Generate
A photorealistic reference made with AI (Sora). The photorealistic view uses this image directly. Licensing was handled by a separate legal team.
Vectorize
In Illustrator, I draw the silhouette and symbolic versions from the same figure.
Import
Export as DXF files and import them into Archicad.
Build
Each drawing becomes a library object users can recolor and resize, then goes to the developers.
note:
Two problems slowed me down at first. Scale: drawing a 25-meter tree at full size in Illustrator isn't practical, so I drew at 1:100 and scaled up on export. Extra lines: imports were full of unneeded lines, so instead of cleaning them by hand I changed my vectorizing setup and export settings until files imported cleanly.
After that, objects went to the developers without back-and-forth. I tracked every object and its status in Excel, alongside Jira and Confluence.
07 — what shipped
Two library releases
303
new 2D trees in Archicad 28 Library Update 1, with style-first selection, new previews, and contour and gradient controls.
501
new 2D people and animals in Archicad 29 Library Update 1, grouped by activity.
Each graphic is available in photorealistic, silhouette and symbolic versions, as an editable, recolorable object.
08 — users
Meeting the people who use it
For the launch, Graphisoft ran the ArchiPET community challenge in early 2026. More than 20 users showed the new figures in their own designs. I joined the roundtable with the 4 winners, walked them through how I made the objects, and then turned their pets into objects in the official library. The surprise: some had already made animated pets inside Archicad. People push a library further than we design for.
09 — what I learned
Order, evidence and restraint
Forum threads are research
Users were already explaining the problem in their own words. Reading them closely gave a clear direction without a formal study.
Order matters as much as options
Nothing was missing from the old dialog. Changing the order of choices was enough to make it match how people work.
Audit before you add
Placing every existing figure in every view showed me what to leave out, like top-view people, before I drew a single new one.
A preview only needs to hint
It has to show the style and suggest there's more. Hierarchy did that better than any icon I tried.




