Questions

Yes, for personal and educational use: the web app and the desktop app, with building together, instructions, renders, exports and share links, AI never limited, and up to 25 models kept with your account. Saving to your device and exporting are never limited. Pro, coming soon at $8 a month or $80 a year, keeps any number of models with your account and adds a licence for commercial use. Nothing takes money yet.

No, never, on any plan. You bring your own AI: your Claude through the connector or Claude Code, or your own Anthropic API key; in the desktop app, your own key for OpenAI, Gemini and others too. Its maker bills your plan or key for what it does, never Brickworks, so Brickworks never counts it or pays for it. The desktop app can also start Claude Code for you.

Nothing you have is taken away. Every account made before 29 October 2026 keeps Pro, free and with no end date: any number of models kept with your account, and commercial use once its terms are out. There is nothing to do.

Free is for personal and educational use. Selling what you make with Brickworks, such as instructions, kits, renders or builds made to order, comes with Pro, under terms that come with it when Pro opens.

Yes: Studio .io (locked ones too), LEGO® Digital Designer .lxf, and LDraw .ldr and .mpd. It saves LDraw, exports glTF, OBJ and STL, saves a booklet as a PDF or PNG pages, and turns OBJ, STL and glTF models into bricks. It writes Studio .io too, but nobody has opened one in Studio yet to check, so LDraw is the surer way into Studio.

Export the parts list as a BrickLink wanted list or a Rebrickable parts list, by the lot, the way shops sell them. My collection first takes off what you already own.

A recent browser on a computer, a tablet or a phone (it runs on WebGL 2 and WebAssembly threads). On a tablet or a phone the app is laid out for a finger: one row of tools, and the parts, the colours and the rest in panels beside the model or, on a phone, sheets over it. Or the desktop app for Linux, macOS and Windows, free like the web app, which carries every part on disk and builds with no network at all.

In the desktop app, from 0.8.0. Every button, part, colour and field says its name (“Select, V”, “Brick 2 x 4, 3001”), and what the status line says is read out. F6 (or Tab, with a screen reader running) goes from the model into the toolbar, the parts and the colours; Return takes a part, and Return again puts it down at the middle of the view. Settings has Interface size, 85 to 150%, and Reduce motion. In a browser the app draws its controls itself, where a screen reader cannot reach them; this site’s own pages work with both.

1 LDU is 0.4 mm exactly, and every dimension was read off the part geometry rather than copied from a reference. The tests assert them, so a library update cannot move them quietly.

Sizes are nominal rather than as moulded, which is what makes parts tile exactly instead of leaving a gap that grows along a long wall. The stud height is the LDraw library's own convention, and every part follows it.

With a code we email you, or with orangecheck: its own window, with a Bitcoin wallet, email, Google or GitHub. Either way there is no password to keep. The desktop app signs in by the emailed code, and with orangecheck from 0.8.0. More on what each keeps.

In your browser, or on your computer in the desktop app, and kept privately with your account too, so they open in File › Open wherever you sign in. Export them as LDraw .ldr to keep or move. Nobody else sees a model until you share it.

Press Reload when it suits you. The model in that tab comes back as it is, under its name. Until then the tab keeps working, but it saves nothing to your saved models, so it can never write over what a tab on the new version keeps. Save again after the reload.

Yes, live. File › Build together… gives a link to your model, and whoever opens it, signed in, builds it with you at the same time in their browser (the desktop app from 0.8.0). Each of you sees the other’s parts go down, move and change colour as it happens, and their pointer with their name; Undo takes back only your own changes, and there is a short chat for people 13 and over. A reload goes back into the session by itself. You end it, and the model stays yours.

Build it opens it in 3D: turn it, step through its build, and get its booklet and parts list, with no account. Open in Brickworks copies it into your own models, to change and make yours; share that, and its page shows it as a remix. Under them you can like it, save it to your favourites or a collection, share its link, comment on it or on one of its steps, and say I built it with a photo of your build. More copies the code to embed it in a page of your own, and is where to report it.

That a person can build it. Brickworks tests a model as it is shared: built in its own steps, each part goes on where something holds it and the model stands at every step; every part is in a colour it was made in; and, finished, every part is held by a stud, a joint or what catches it, no two passing into each other, by the parts’ real shapes. A model that is not marked tells its owner why on its page.

No. Everything but the assistant works without one, and the assistant is off until you turn it on in Settings, Assistant, or open the app with it on: build entirely by hand and there is no AI anywhere in the window. To bring Claude in, turn it on, then connect your Claude account, or paste an API key from the Anthropic Console.

No. It stays in your browser or on your computer, or only for the visit if you choose, and is sent only to the AI you chose: in a browser, Anthropic. The page's security policy refuses to send anything anywhere but its own short list, so a key has nowhere else to go. More on what Brickworks keeps.

Brickworks tells Claude when its tools change, and a Claude app that listens for that picks them up by itself. If yours hasn’t, reload the Brickworks tab first if it says it has been updated. Then start a new conversation. If the tool is still missing, reconnect Brickworks in Claude: Customize › Connectors, select Brickworks, Disconnect, then Connect; in Claude Code, run /mcp, choose brickworks and Reconnect. Not Disconnect Claude in Brickworks: that ends Claude’s connection, and you connect it and allow it again.

Yes, in Claude: Customize › Connectors, select Brickworks, and under Tool permissions choose Always allow for the tools you trust, or press Always allow when Claude asks. Those switches are Claude’s, so Brickworks cannot set them for you. It does tell Claude which of its tools only look and change nothing. Brickworks asks you to Allow once, and not again while Claude stays connected. To connect again after a Disconnect, press Connect on the Brickworks already in your connectors rather than adding it again: adding it again sets up a new one, with its tool permissions to choose again.

Studio is the community’s standard and does a lot well. Brickworks runs in any browser, a tablet’s or a phone’s too, with nothing to install; weighs balance and joint strength, and lists the weakest joints; turns gear trains at their real ratios; opens Studio .io; exports STL, OBJ and GLB; and builds one model with others, live. See it beside Studio, Mecabricks, LeoCAD and LDCad, with where each of them still leads.

No. LEGO® is a trademark of the LEGO Group of companies which does not sponsor, authorize or endorse this site. The parts come from the community's LDraw library, and the catalogue data from Rebrickable.