Show the material and what it means
Rendering tools show what a material looks like. They do not say how much of it the design needs, which product it is, where the rate came from, or how a quantity was measured. Those answers usually live in a separate spreadsheet that drifts from the model.
Material Studio keeps them together. You assign materials the way you would in a real-time renderer, and the estimate reads quantities from the model’s geometry, with product references, rate status and a schedule you can hand to an estimator or client.
It is for landscape architects, architects and designers making material decisions at the design stage.
How it works
- Export glTF (.glb) from your modeling tool. Name materials meaningfully in the source model; each becomes a surface.
- Open the model and check the size readout. Set units or the up axis if the model reads wrongly. Demo scene asks before it replaces your model, and Undo brings it back while the page stays open.
- Select and apply. Click a surface and choose a library material, or choose a material and paint it onto surfaces. Choosing another material while painting switches to it; the surface just painted keeps its material.
- Choose how each quantity is measured, or type a quantity to override the measurement. An entered quantity cannot be negative. Every schedule line says whether its quantity was measured or entered.
- Read the estimate: totals by category and a schedule with tag, product reference, quantity, rate, rate status and amount. A total with any priced line using a placeholder rate is labeled “Illustrative total”, and a total that mixes supply-only, delivered and installed rates is flagged. Lines priced in different currencies get a subtotal and total for each currency; amounts are not converted or added together, and with more than one currency there is no single total and no totals by category. Estimate basis and Exclusions, after the schedule, are free text you write.
- Mark up a rendering from any renderer by drawing zones and tagging them; for a plan or elevation drawn to scale, areas are measured.
- Export the schedule as CSV, the view with tags and schedule as an image, the project as JSON, or the library as CSV, or print the schedule as a sheet to save as PDF. The schedule CSV, the image and the sheet state the estimate basis and exclusions. Saved CSV files start with a UTF-8 byte-order mark, and a text cell that starts with =, +, - or @, a tab or a line break gets a leading apostrophe so a spreadsheet does not run it as a formula. Import your own supplier list as CSV, in US customary or metric units.
On a phone, one panel shows below the view at a time, chosen with a switcher: Materials, Surfaces or Project (Selection when something is selected). When the open estimate would cover more than 40% of the view’s width, it starts collapsed; Show expands it.
How quantities are measured
- Upward faces (sloped area)
- Faces pointing up within 45° of horizontal, at their true sloped area, not projected onto a plan: paving, planting, decking. Earlier builds called this rule Plan surfaces; projects saved then load unchanged.
- Vertical faces
- Faces steeper than 45°, both sides of a wall: cladding and veneer.
- All faces
- Every face, for objects finished all round.
- Placed items or mesh pieces
- Placed items (each top-level group or component once per schedule line, even across several surfaces) or mesh pieces: trees, furniture, fixtures. The panel lists what was counted; check those names. A group containing all trees counts as one item. Ungroup in the source model before export, or choose mesh-piece counting when that matches the objects.
- Entered
- A number you type, for linear items or anything the model does not describe.
Volume items multiply the measured area by the material’s thickness. Waste is added per item and contingency on the subtotal. Items marked “by others” stay visible but are excluded from the total.
Supported software
glTF 2.0 exported from SketchUp, Rhino, Revit, Blender, Twinmotion or similar, natively or through a plug-in depending on the program and version; exports from these programs have not been tested with the app. A current browser with WebGL 2 is required. Printing, the phone layout and keyboard use have been checked in Chrome only; other browsers and screen readers have not been checked for them.
What changed in v0.3
- Any placeholder rate makes its total illustrative. Each currency is checked separately. A placeholder line without a usable rate contributes nothing to the total.
- Placed items count once per schedule line. A tree assigned through its trunk and canopy counts once on the same material line. Separate material lines count separately; mesh-piece counting is unchanged. Reopened saved projects use the new rule, so quantities and amounts can decrease when several surfaces counted the same items. Check the estimate after reopening.
- CSV price bases use readable labels: Supply only, Delivered, Installed and Not stated. Library import still reads the earlier keys. When only some priced lines state a basis, a quiet note names how many do not.
- Shorter rendering-replacement notices, US spelling and a one-line version badge on phones. New projects use the revised exclusions text; saved text stays as written.
The v0.2 connection to Base Plan remains: a model and to-scale plan arrive through this browser’s storage, the app asks before replacing different work, and a reload reopens the retained model.
These changes were checked in Chromium with automated tests. Safari, Firefox, screen readers, real supplier lists and real SketchUp or Rhino exports and models near the 64 MB hand-off limit have not been tested. The app repository has 186 passing tests; this is not an accuracy assessment.
Limitations
- A design-stage material estimate, not a contractor bid or cost plan. Labor, site preparation, installation, overhead and profit, and escalation are excluded unless your rates include them. New projects start with that exclusions list; saved text is kept as written. Edit it to say what your estimate leaves out.
- The sample library is generic and its rates are placeholders. It names no products or suppliers; import your own.
- Quantities come from the model’s triangles. Overlapping or hidden geometry, double-sided walls or wrong units flow straight into the numbers. Check before relying on them.
- Perspective renderings are not to scale, so their quantities must be entered.
- Compressed glTF (Draco or meshopt), GPU-instanced copies and sparse accessors are reported and not read; export uncompressed .glb.
- Amounts in different currencies are not converted; each currency is totaled on its own.
- Real-time lighting for making decisions, not a replacement for your renderer.
Questions
Is it free?
Yes, it is free to use.
Is my model uploaded?
No. The app is a single web page; your model is read in your browser and the app does not send it anywhere. Your project is saved in this browser, and a model that arrived from another Field Method page is kept there too, so a reload can reopen it; clearing the site’s data removes them.
Can I use my own rates?
Yes. Import a supplier list as CSV; the app reports any columns it does not recognize. A negative rate, waste or thickness is refused and reported, and when two rows share a code, the last one replaces the others and the report names the rows.
Related: Corridor Studio

