Archicad 2D Library — Trees, People & Animals

Redesigning tree selection in Archicad's library and producing 804 new 2D graphics of trees, people and animals.

Making Archicad's 2D library easier to browse and richer to draw with.

Forum users told us that finding the right tree in Archicad's library was harder than it should be. I redesigned tree selection so architects pick the drawing style they need first, and added contour and gradient controls. I also produced 804 new 2D graphics with an AI-assisted workflow: 303 trees in Archicad 28, and 501 people and animals in Archicad 29.

Year

2025

2025

Role

Product Designer · Archicad Library

Product Designer · Archicad Library

Work type

Web App

Web App

Project scope

Library UX, Interaction Design, Illustration, AI-assisted Production, Workflow Design, User Roundtable

Collaboration

Product manager, 3 developers, 2 QA

Context and my role

Archicad is Graphisoft's BIM software for architects. Its object library includes 2D graphics of trees, people and animals that architects place in plans, sections and elevations. They make drawings readable and show scale, and they need to match the drawing style of each project.

I worked on two library updates. In Archicad 28, I redesigned how users choose trees and added new display controls. Across Archicad 28 and 29, I produced new 2D graphics and built them into editable Archicad objects. I worked closely with a product manager, 3 developers and 2 QA engineers throughout.

The problem

In the old Object Selection dialog, users chose trees by biological attributes first, such as species. Feedback in community forum threads showed that this doesn't match how architects work. They first decide how a tree should look in the drawing: photorealistic, silhouette or symbolic. The species usually comes second.

The library also needed more content. Projects need many kinds of trees, people and animals, each in every drawing style, and the existing set didn't cover that.

Constraints

  • Volume. Hundreds of graphics, each needed in three drawing styles, without losing consistency.

  • They had to be real Archicad objects. Users needed to recolor and resize them like any other library element, not just place flat images.

  • A mature, widely used library. Changes to the selection dialog had to fit existing conventions that many users already know.

Process and key decisions

1. Start from the drawing style, not the species

I changed the order of tree selection. Users now choose the view they need first, photorealistic, silhouette or symbolic, and then pick the tree. This matches the decision architects actually make first, based on the style of the drawing they're working on.

2. More control over how trees look

I added two controls to all silhouette and symbolic trees: a contour line on/off switch and gradient fill settings. Architects can now match trees to the graphic style of each project without editing the objects by hand.

3. 2D only, by design

The old library objects combined a 2D symbol and a 3D representation in one element. In 3D, an old bug showed their images as empty billboards, and we didn't have the capacity to fix it. Instead of adding hundreds of new objects that would look broken in 3D, we looked at how these objects are actually used: mostly as 2D figures in sections and elevations. So the new trees, people and animals became 2D-only objects, and 2D and 3D became separate elements.

This also meant we weren't taking anything away. Because of the bug, the 3D view didn't work for anyone, so even users who wanted it couldn't rely on it. Making the new objects 2D-only removed nothing that worked, and it let us focus our limited capacity on the views people actually use.

The harder question was what happens to objects already placed in users' projects. First, I mapped every case on a Miro board: how old 3D and 2D versions could migrate, and what users would see in each view.

📷 IMAGE: The Miro migration board, redrawn cleanly.

In the end, I proposed a simpler approach than converting old objects. Old objects stay exactly as they are, and the new ones sit next to them in separate folders of the same library package. I weighed how much development work each option needed, how likely it was to be built, and what users would experience. Converting objects meant more work and more risk of breaking existing projects. Keeping both meant no project changes when users open it.

To decide what goes where, I proposed one rule: 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. Old 3D-capable trees and new 2D trees look different and serve different purposes, so they stay separate, each in its own folder. The team agreed.

4. A production workflow built for volume

I made all 804 graphics myself, so I set up a workflow that could handle the volume:

  1. Generate a photorealistic reference with AI, using Sora. These work as images in Archicad, so they could be used directly.

  2. Vectorize the reference in Illustrator to create the silhouette and symbolic versions.

  3. Export them as DXF files and import them into Archicad.

  4. Turn each drawing into a library object that users can recolor and resize, then hand it over to the developers.

The hardest part was keeping track. Hundreds of objects, three views each and ongoing updates meant I needed a clear record of every object, its type and its status. I tracked every object in Excel. With the team, I used Jira to stay on track and Confluence for documentation, alongside Teams chats and calls.

Two problems slowed things down at first:

  • Scale. Archicad objects need real-world sizes, but drawing a 25-meter tree at full size in Illustrator isn't practical. I drew everything at 1:100 and scaled it up on export, so each object matched its real size in Archicad.

  • Extra lines. After import, the drawings came in with many unneeded lines that I had to remove by hand. I fixed this at the source: I changed my vectorizing setup in Illustrator and tested export settings until the files imported cleanly into Archicad.

I refined the workflow until neither problem came up anymore. After that, objects went to the developers without back-and-forth.

Outcome

Both updates shipped in official Archicad library releases:

  • Archicad 28 Library Update 1: 303 new 2D trees, view-first tree selection, and contour line and gradient fill controls.

  • Archicad 29 Library Update 1: 501 new 2D people and animal graphics.

That's 804 graphics in total, each available in photorealistic, silhouette and symbolic views, as editable and recolorable objects.

Taking it to users: the ArchiPET challenge

To launch the new people and animals, Graphisoft ran the ArchiPET challenge from January 21 to March 15, 2026. Users submitted Archicad views showing the new 2D figures in spaces they had designed, and could add their own pets as custom images.

More than 20 users took part, and the jury picked 4 winners. I joined the roundtable with the winners and the product manager, and gave a short walkthrough of how I made the 2D objects. Afterwards, I turned the winners' pets into objects in the official Archicad library.

Talking to users directly taught me things I wouldn't have guessed:

  • They push the library further than we expected. Some had made animated pets inside Archicad.

  • They use the community in different ways. One winner answers other users' questions. Another encourages her students to ask questions and take part.

  • Seeing their own work in the product matters. The winners were genuinely excited to have their pets in Archicad and to talk with the team behind it.

What I learned

  • 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.

  • AI is a starting point, not the result. It made the volume possible, but each graphic still needed design judgment to work in a professional drawing.

  • Meet the people who use your work. Forum threads told me what was wrong. Talking to users at the roundtable showed me how they actually use the library, and how much it means to them to see their own work in the product.

← all work

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.

Role

Product Designer · Library

Team

Product manager, 3 developers, 2 QA engineers

Year

2024–2026

Scope

Forum researchInformation architectureInteraction designProduction workflow

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

a

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.

species firstdrawing style first
BeforeAfter

Tree selection before and after the redesign.

a

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.

Preview iterations: equal grid, folder metaphor, overlapping trees.

a

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

a

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.

b

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.

c

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 plan we didn't ship: migrate every old object3D versions → billboardlook the same as before2D versions → silhouettebut not every 2D has a 3D versionan old people symbol placed on…1 · a section or elevation2 · a floor plan, 3D off3 · a floor plan, 3D billboard onnever shows in 3D,always a symbolset to symbol only,3D turned offshows on the plan andas a billboard in 3D→ migrate to a contour-only objectbecomes a plain 2D symbol→ migrate to the billboardkeeps its 2D symbol, but symbolview can't be turned offexception: for symbol only,users must pick another elementwhat I proposed insteadKeep the old objects where they are.Put copies in the new folders, next to the new ones.Copies get the same new controls. No conversion, no exceptions.three cases, each with its own exceptions, so ↓

The migration plan we didn't ship: three cases, each with its own exceptions. Mapping it out is what made the simpler option obvious.

a

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.

b

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.

1

Generate

A photorealistic reference made with AI (Sora). The photorealistic view uses this image directly. Licensing was handled by a separate legal team.

2

Vectorize

In Illustrator, I draw the silhouette and symbolic versions from the same figure.

3

Import

Export as DXF files and import them into Archicad.

4

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.

next: your team?

Right now

Looking for a mid-senior product design role in B2B SaaS or fintech. Available from December 2026.

© 2026 Karola Menyhárt · Budapest

Built in Framer