Forma studies the site. Rayon draws the room.

A planning meeting starts with a parcel, a sun angle and a nervous density target. A drawing meeting starts with a wall that needs the correct thickness. Forma Site Design belongs in the first room. Rayon belongs in the second.

The search phrase “forma site design vs rayon” makes the pair sound like rival CAD packages. They are not. Autodesk presents Forma Site Design as cloud software for contextual site setup, massing and early analysis. Rayon presents itself as a web-based 2D drawing and presentation system. One asks what the site permits. The other asks whether the linework can carry the conversation.

What is the real difference between Forma and Rayon?

Forma begins with geography. Autodesk's setup guide starts from an address or coordinates, then orders available roads and buildings into a geolocated canvas. A designer draws a site limit, places massing and compares proposals against contextual information.

Rayon begins with a drawing. Its workspace is built around 2D geometry, layers, blocks, styles and pages. Rayon's own FAQ states plainly that it is a 2D tool, not 3D software. That sentence should end most confused comparisons. A massing engine and a collaborative drafting surface can exchange references, but they do not solve the same problem.

This is a familiar procurement mistake: compare two products because both appear under “early design.” Early design is not one task. Site capacity, environmental response, plan development and client communication can happen in the same week while demanding very different representations. Our category-error guide explains why a shared phase does not make two tools interchangeable.

Forma earns its seat with context and analysis

Autodesk has made Forma's scope unusually clear. Its August 2026 tool overview documents proposal layers, contextual data, 3D sketching and side-by-side comparison. The same page describes sun hours, daylight potential and wind among the analyses available from the model. These are vendor-documented capabilities, not proof that every result is fit for a planning submission.

Still, their location inside the option model matters. A height change can be examined where the geometry and site context already live. The point is less button speed than conversational speed: the team can connect a design move to an early indicator before the move hardens into a drawing package.

Forma also keeps bases separate from proposals. Autodesk's overview says one base can serve multiple proposals, while proposal layers can be duplicated and compared. That structure suits the politics of early design. The site is treated as a shared condition; the schemes remain alternatives. A giant copied CAD file can represent the same distinction, but it rarely makes the distinction pleasant.

The product is not a substitute for specialist simulation or code review. Autodesk calls these early analyses, and that adjective should stay attached. Our daylight analysis warning applies here too: a quick indicator informs a question; it does not certify an answer.

Rayon wins when the design becomes a drawing

Rayon's strength is humbler and, in many offices, more immediately useful. Its import and export documentation covers DWG, DXF, PDF and image routes. Existing references can enter the browser, be scaled and become the basis for editable plan work. That is a much shorter trip from consultant PDF to marked-up scheme than building a site model.

Blocks carry repeated objects. Rayon's block documentation says imported AutoCAD blocks can become Rayon blocks, with instances tied to a shared definition. The mechanism is ordinary CAD logic, which is praise. Doors should behave like doors before an AI assistant writes a sonnet about them.

Rayon also treats presentation as part of drawing production. The architect page says plans can be styled, placed into pages and exported for print or shared by URL. Live browser editing and shared libraries address the coordination work around a drawing, not merely the act of making one. That makes Rayon a credible option for space planning, feasibility layouts and client-facing sets that do not yet need a full BIM authoring system.

The ceiling is equally clear. Rayon's FAQ says the product is 2D. If the decision depends on terrain, facade exposure or a volumetric relationship, forcing Rayon to answer it turns a clear plan into a stack of assumptions. Use the plan to communicate what the plan knows.

Can Forma Site Design and Rayon work together?

Yes, but the exchange should be modest. Forma can export views as SVG or PNG according to Autodesk's 2026 tool overview. Rayon accepts PDFs and images as references, and its import guide supports scale setup for incoming material. That provides a route for a site diagram or plan reference, not a live bidirectional model.

A sensible sequence is to resolve parcel, massing and early performance in Forma, then send a controlled 2D reference into Rayon for plan development and presentation. Record the export date, scale and proposal name. When the massing changes, replace the reference rather than quietly drawing over yesterday's evidence.

If the project is heading to Revit, do not invent a Forma-to-Rayon-to-Revit relay merely because every step can emit a file. Autodesk says Forma can turn its proposal into a geolocated Revit project on the product page. Test that direct route first. Each extra translation is another place for coordinates, units and object meaning to loosen.

Our native integration audit offers the right principle: file support is a transport claim, while usable continuity is a project claim. Check scale, origin and revision identity at the boundary.

Which tool should a small architecture practice buy?

Buy Forma when site acquisition, planning options or environmental questions are frequent enough to justify a dedicated pre-design model. Autodesk currently lists Forma Site Design at $59 per month and says it is included with the AEC Collection on its official product page. Regional prices and terms can change, so confirm the checkout that applies to the office.

Buy Rayon when the recurring pain is 2D production: traced plans, space studies, blocks, page layouts and browser review. Rayon's official FAQ says limited use is free and paid plan details sit on its pricing page. Price alone is a poor tie-breaker here because the products remove different labor.

Trial the decision, not the demo. Give Forma one awkward parcel and require two massing proposals with an analysis question. Give Rayon one consultant background and require a revised plan plus a presentation page. Time the second revision, because first-pass speed is where polished software demonstrations keep their makeup.

Then inspect the handoff. In Forma, ask whether the receiving BIM author trusts the coordinates and geometry. In Rayon, ask whether another designer can edit the drawing without an oral history from its maker. The winning product is the one that reduces the office's actual uncertainty.

Do not ask a site model to win a drafting contest

Forma Site Design has the stronger answer when the unresolved object is the site. Rayon has the stronger answer when the unresolved object is the plan. Their overlap consists mostly of browser access, early timing and the word “design.” That is thin grounds for a duel.

The sharper comparison is between risks. Forma reduces the risk of choosing a mass without enough context. Rayon reduces the risk of turning fast plan work into disconnected files and presentation redraws. A practice may need either one, both or neither.

Put the parcel in Forma. Put the lineweight in Rayon. Stop asking the screwdriver to read the weather.

Sources checked

Product claims were checked on 1 November 2026 against Autodesk's current Forma product page, getting-started help and August 2026 tool overview, plus Rayon's current architect page, FAQ and documentation for import, export and blocks. Vendor descriptions are identified as such, and no hands-on performance claim is made.