How to Convert Revit to Excel Without a License

Q: Can you convert Revit to Excel without a license?

Yes. It reads .rvt files directly, no Revit installation required. The Community version is free and works offline.

Q: What format is the output?

.xlsx, standard Excel format. Opens in Excel, Google Sheets, LibreOffice, anything that reads Open XML. You also get .dae (3D geometry) and optionally .pdf sheet exports.

A common request: get the data out of a Revit® file on a machine without Revit. Not everyone on a team has an Autodesk® Revit seat, and checking element quantities or parameter values in a spreadsheet does not need one.

The Revit to Excel converter in the CAD2DATA Pipeline reads .rvt files directly and writes a structured .xlsx workbook with all elements, all parameters, geometry data and bounding boxes. No Revit on the machine. No Autodesk account. No plugins. Works on Windows® and Linux, runs offline. The code, workflows and samples live in the cad2data repository on GitHub.

Below are four ways to run it, from a single file to batch pipelines.

Typical uses

Once the model is a table, it can be processed in Excel®, Python™, Power BI or a database. Typical uses:

Quantity takeoffs: element counts, areas, volumes, lengths. Apply unit rates in Excel, build cost estimates, also across several models at once.
Data validation: check if parameters are filled, naming conventions match, classification codes are correct. A short pandas script checks every element of a model in one run.
ERP integration: SAP, Oracle, MS Project all take Excel or CSV as input. The converter gives you structured data ready to import.
AI and ML workflows: once you have tabular data, you can run classification, cost prediction, anomaly detection. Tables can also be passed to a language model for analysis.

What exactly comes out?

Every element in the model gets a row. Every parameter gets a column. The output workbook contains:

Category	What you get
Identity	ElementId, UniqueId, Category, FamilyName, TypeName
Geometry	Area (m²), Volume (m³), Length (m), Perimeter
Location	Level, Room, X/Y/Z coordinates
Bounding box	Min/Max XYZ, useful for clash detection and spatial queries
Parameters	All of them. Instance and type. Custom parameters too.
Materials	Material name, category
Schedules	Each Revit schedule view becomes a separate sheet in the workbook

You also get a .dae file (3D geometry in COLLADA format, element IDs match the XLSX) and optionally .pdf exports of sheet views.

Method 1: n8n™ workflows

n8n runs the workflows in a browser interface on your own machine, without writing code.

git config --global core.longpaths true
git clone https://github.com/datadrivenconstruction/cad2data-Revit-IFC-DWG-DGN.git
cd cad2data-Revit-IFC-DWG-DGN
npx n8n

Open http://localhost:5678, import one of the ready-made workflows from DDC_n8n_Workflows&Pipelines/, set your file path in the “Set Variables” node, and click Execute.

The repository contains 9 workflows. Six of them:

Workflow	Description
`n8n_1_*`	Basic conversion: RVT/IFC/DWG™/DGN to Excel
`n8n_2_*`	Full Revit export with bounding boxes, schedules, PDF sheets
`n8n_3_*`	Batch convert a folder with validation and HTML report
`n8n_5_*`	AI classification using LLM + vector search
`n8n_6_*`	Automated cost estimation
`n8n_7_*`	CO₂ carbon footprint calculation

Requires Node.js® 18 or later.

Method 2: Command line

Without n8n, call the converters from a terminal. They are standalone executables. One input, one output.

RvtExporter.exe "C:\Projects\Building.rvt"

That gives the default export (XLSX + DAE). Options follow the file name:

RvtExporter.exe "C:\Projects\Building.rvt" standard bbox schedule sheets2pdf

This gives the standard export mode (724 categories) + bounding boxes for every element + schedule exports + PDF sheets. The other export modes are basic (309 categories), complete (1209 categories) and custom (your own category list in a .txt file). room adds ToRoom/FromRoom data, -no-xlsx and -no-collada switch off an output. The output lands next to the input file.

Long paths on Windows: the repository has deeply nested folder names. Git reports “Filename too long” unless you enable long paths first:

git config --global core.longpaths true

And always use full absolute paths when calling the converter. Relative paths will fail silently or produce empty output. Use %CD%\ prefix or spell out the full path.

CLI reference

Input	Command	Output
.rvt / .rfa → Excel	`RvtExporter.exe file.rvt [basic\|standard\|complete\|custom] [bbox] [room] [schedule] [sheets2pdf]`	XLSX + DAE (+ PDF)
.rvt / .rfa → IFC	`RVT2IFCconverter.exe file.rvt [preset=standard\|extended\|custom]`	IFC
.ifc → Excel	`IfcExporter.exe file.ifc`	XLSX + DAE
.dwg → Excel	`DwgExporter.exe file.dwg`	XLSX + PDF
.dgn → Excel	`DgnExporter.exe file.dgn`	XLSX

Method 3: Python scripts

The converter is an executable, so you can call it from Python with subprocess, then process the output with pandas or whatever you like.

Single file:

import subprocess

result = subprocess.run([
    r"C:\DDC\RvtExporter.exe",
    r"C:\Projects\Model.rvt",
    "standard", "bbox"
], capture_output=True, text=True, timeout=300)

print("OK" if result.returncode == 0 else result.stderr)

Batch convert a whole folder and then analyze:

from pathlib import Path
import subprocess, pandas as pd

converter = Path(r"C:\DDC\RvtExporter.exe")

for f in Path(r"C:\Projects").glob("*.rvt"):
    print(f"Converting {f.name}...")
    subprocess.run([str(converter), str(f), "standard", "bbox"],
                   capture_output=True, timeout=600)

# Now work with the data
df = pd.read_excel("Model_rvt.xlsx", engine="openpyxl")
walls = df[df["Category"].str.contains("Wall", case=False, na=False)]
print(f"{len(walls)} walls, total area: {walls['Area_m2'].sum():.1f} m²")

You’ll need pip install pandas openpyxl for the analysis part. The converter itself has no Python dependencies.

Method 4: Docker® and Linux

For reproducible environments or Linux servers. The converters are available through our APT repository, so a Linux Dockerfile is straightforward:

FROM ubuntu:22.04
RUN apt-get update && apt-get install -y curl && \
    echo "deb [trusted=yes] https://pkg.datadrivenconstruction.io stable main" \
    > /etc/apt/sources.list.d/ddc.list && \
    apt-get update && \
    apt-get install -y ddc-rvtconverter ddc-ifcconverter
WORKDIR /data
ENTRYPOINT ["ddc-rvtconverter"]

docker build -t ddc-converter .
docker run --rm -v /your/projects:/data ddc-converter /data/Building.rvt /data/output/

The repository README also shows a Windows container example that copies the Windows converter folder into the image.

Scaling up: batch processing and CI/CD

Options for hundreds of files:

n8n batch workflow: import n8n_3_*.json. It walks a directory, converts each file, validates the output, and generates an HTML summary report.

GitHub® Actions: put the converter in a CI pipeline. On every commit or on a schedule, convert the CAD files and store the Excel output as build artifacts.

AI coding assistants: the repository includes instruction files in AI_AGENTS_INSTRUCTIONS/ (including CLAUDE.md). Open the repo in Claude™ Code, Cursor™, or similar, and describe the task in plain language, for example: “Convert all .rvt files in this folder and show me a summary of wall types.” The assistant reads the instructions and runs the commands.

Converter and Revit’s own export

As of October 2026, based on the cad2data README and Revit’s documented export menu.

	RvtExporter.exe	Export from Revit
Needs Revit installed	No	Yes
Runs on Linux	Yes (APT package)	No
Command line	Yes	No, started from the Revit interface
Output	XLSX, DAE, PDF sheets; IFC via RVT2IFCconverter	Schedules as TXT, plus DWG, IFC, PDF and other formats

When another tool fits better

The converter only reads. To write changed values back into a Revit model, use a Revit add-in with two-way Excel sync, which runs inside Revit and needs a Revit licence.

FAQ

Can you convert Revit to Excel without a license?

Yes. It reads .rvt files directly, no Revit installation required. The Community version is free and works offline.

What data gets extracted from an RVT file?

Element IDs, categories, families, types, all instance and type parameters, geometry (area, volume, length), location (level, room, coordinates), bounding boxes, materials. Schedules export as separate sheets. Custom parameters are included automatically.

Does it work with Revit 2026?

Yes. Supports versions 2015 through 2026. The converter reads the native file format directly, no version downgrade needed.

Can I batch convert multiple files?

Yes. Use the n8n batch workflow, a Python script looping over a directory, or a simple shell loop. The converter processes one file per call, so batch just means calling it in a loop. Parallelization works too.

Is it free for commercial use?

The Community version is free for personal and research use. Commercial use in a revenue-generating capacity, SaaS deployment, third-party file processing or redistribution of the binaries needs a commercial licence. Contact info@datadrivenconstruction.io for a quote.

What format is the output?

.xlsx, standard Excel format. Opens in Excel, Google Sheets, LibreOffice, anything that reads Open XML. You also get .dae (3D geometry) and optionally .pdf sheet exports.

Download


Licence:	Community version free for personal and research use; commercial licence on request. Workflows, scripts and docs: MIT
Requires Revit:	No
Platforms:	Windows® 10/11 64-bit, Linux (CLI, APT, Docker®)
Output formats:	XLSX, DAE, PDF; IFC via RVT2IFCconverter
Batch & CI/CD:	Yes: unlimited files, n8n™ workflows, GitHub® Actions
AI integration:	Yes: Claude™ Code, Cursor™, Copilot™

Get it on GitHub
Revit to Excel converter: download and details

If it saves you time, a star on GitHub goes a long way.

Working with other formats? See our guides for IFC to Excel, DWG to Excel, DGN to Excel, RVT to Excel, and Revit to IFC conversion.

Revit® and AutoCAD® are registered trademarks of Autodesk, Inc. DWG™ is a trademark of Autodesk, Inc. Excel®, Windows®, Power BI® and Copilot™ are trademarks or registered trademarks of Microsoft Corporation. Docker® is a registered trademark of Docker, Inc. GitHub® is a registered trademark of GitHub, Inc. Node.js® is a registered trademark of the OpenJS Foundation. Python™ is a trademark of the Python Software Foundation. n8n™ is a trademark of n8n GmbH. Claude™ is a trademark of Anthropic, PBC. Cursor™ is a trademark of Anysphere, Inc. All other trademarks are the property of their respective owners. This project is not affiliated with or endorsed by any of the above companies.