Add Custom IFC, RVT, NWD Properties

Create new property sets with custom parameters on selected IFC elements.

Besides IFC, this tool takes Revit (.rvt) and Navisworks (.nwd) files, with no Revit or Navisworks licence. Drop one in and it is converted to IFC first, then the tool runs on that IFC; your original file is not changed.

Add a property set to an IFC model online — define the set name, list the parameters and their data types, pick which elements get them, and download the model with the new data attached. No authoring seat, no round trip through Revit or Archicad, nothing installed.

Almost every IFC hand-off is missing something the next person downstream needs. The structural model has no cost codes. The architectural export dropped the asset tags facilities asked for. The consultant's file has geometry but none of the classification data your checker validates against. Re-exporting from the authoring tool means going back to whoever owns the model and waiting; adding the properties directly to the IFC takes one pass here.

When to reach for it: When you need to add custom metadata to elements — like room numbers, fire ratings, cost codes, or any project-specific parameters.

What you get: An IFC file with new property sets added to the selected elements.

Example: Add a 'CostCode' parameter to every IfcDoor before exporting a schedule.

Define the set once, apply it to hundreds of elements

A property set is a named group of parameters. You give the set a name — the buildingSMART convention is a Pset_ prefix for standard sets and a company prefix for your own, so Pset_DoorCommon or ACME_AssetData — and then add as many parameters as you need, each with a name, a value and a data type.

Four data types are available, and the choice matters more than it looks: a value written as Text reads as a string to every downstream consumer, so a cost stored as text won't sum in a schedule and a flag stored as text won't evaluate as a boolean in an IDS check.

Text — labels, codes, notes, anything free-form. Written as IfcText.
Integer — counts and whole numbers, written as IfcInteger so schedules aggregate them.
Real — measurements, costs, ratios; written as IfcReal and safe to sum or average.
Boolean — true/false flags, written as IfcBoolean so IDS and rule checks can test them without string comparison.

Choose exactly which elements get the data

Applying a set to the whole model is rarely what you want. Target by IFC class to give every IfcDoor a CostCode and nothing else; target by saved search to hit a rule ("every fire-rated wall", "everything on level 3") that stays correct as the model changes; or target the exact elements you have selected in the 3D viewer.

Spatial containers are always skipped — the site, building and storey structure never receives element properties, so a run scoped to "all elements" can't accidentally hang a CostCode off IfcBuildingStorey. When both a selection and a class filter are set, the selection wins, so a hand-picked set of elements is never widened by a class filter left over from an earlier run.

Add several sets in one run, and save the recipe

One run can carry several property-set definitions at once, each with its own target scope — so a single pass adds the cost data to the doors, the asset data to the equipment, and the classification data to everything. Save the whole definition as a named preset and recall it on the next revision instead of retyping twenty parameters, or drop it into a saved pipeline so the properties are re-applied automatically every time a new model lands.

If you need to fill in different VALUES per element rather than one value across a class, export the model to Excel first, fill the column in the spreadsheet, and import it back — elements are matched by GlobalId, and the import creates the property set if it doesn't exist yet.

Using it on Revit and Navisworks files

When you open a .rvt or a .nwd file here, BIMCamel converts it to IFC on the server and brings you back to this tool with the converted model loaded. Element ids, levels and properties come across under their Revit and Navisworks names, so pick properties as they appear in your model. Your .rvt or .nwd itself is never edited: a tool that changes the model gives you an IFC back.

Revit files can be up to 25 MB without an account, 100 MB with a free one and 200 MB on a paid plan. Navisworks files can be up to 25 MB without an account, 100 MB with a free one and 200 MB on a paid plan, and they open in the browser viewer at the same sizes. Revit projects saved in Revit 2021 to 2027 are supported.

How to add property sets to an IFC file online

Upload your model (IFC, RVT or NWD)
Define new property sets: name, parameters, and target elements
Click Run to inject the properties
Download the updated IFC file

Under the hood

BIMCamel parses IFC files in the browser using the open-source web-ifc engine and renders models with @thatopen/components + three.js. Heavy operations (clean / optimise / validate / convert) run on disposable server-side workers using the same web-ifc stack plus our own .NET pipeline; results stream back to your browser as soon as they're ready. Uploads sit on our servers only as long as your tier's retention window allows and are never used to train AI.

Frequently asked questions

Can I add a property set to an IFC file without Revit?

Yes. Upload the IFC here, define the set name and its parameters, pick the elements, and download the result. The property set is written into the IFC itself as a proper IfcPropertySet related to each element, so any IFC-aware tool reads it — no authoring licence involved at any point.

What data types can a property have?

Text, Integer, Real and Boolean, written as IfcText, IfcInteger, IfcReal and IfcBoolean respectively. Pick the real type rather than defaulting to Text: a cost stored as text won't sum in a downstream schedule, and a flag stored as text won't evaluate as a boolean in an IDS check.

Can I apply a property set to only some elements?

Yes — target by IFC class (every IfcDoor), by saved search (every fire-rated wall), or by an explicit selection made in the 3D viewer. Spatial containers — site, building, storey — are always excluded, so an "all elements" run never attaches element data to the spatial structure.

How do I give each element a different value?

Add the property here to create the set on every target element, then use Extract IFC Data to export those elements to Excel, fill in the per-element values, and push the sheet back with Excel to IFC. Rows are matched to elements by GlobalId.

Will this overwrite property sets the model already has?

No. Adding a set leaves the model's existing property sets alone. To change what's already there, use Edit IFC Properties for renames and deletions, or Excel to IFC to update values in bulk.

Which IFC versions are supported?

IFC2x3 and IFC4 — the two schema versions exported by essentially every AEC authoring application. IFC4x3, the infrastructure schema, works too: it opens in the viewer, and validation, health reports, property-set editing and georeferencing all run on it. Tools that need geometry processing, such as clash detection and 3D export, aren't verified on IFC4x3 yet.

What's the maximum IFC file size?

Up to 25 MB as a guest, 100 MB with a free account, 500 MB on Pro, and 1 GB on Team. The caps are on upload size only — every tool itself is available on every tier.

What happens to my file after processing?

Your file is uploaded over HTTPS and processed on our servers. Guest uploads are stream-only — the working files are deleted as soon as your download finishes. Free accounts keep results for 7 days; Pro and Team keep saved models until you delete them. Files are never shared with third parties or used to train AI.

Is Add Custom IFC Properties free?

Yes. Add Custom IFC Properties is free to use — guests get 3 runs a day with 25 MB uploads, and a free account raises that to 10 runs a day with 100 MB uploads. No trial clock, no watermarks.

Can I use a Revit or Navisworks file with Add Custom IFC, RVT, NWD Properties?

Yes. Open a .rvt or .nwd file and it is converted to IFC first; the tool then runs on that IFC and your original file is not changed.