Validate IFC Element Names

Check every element's Name follows a token pattern (e.g. {class}-{storey}-{index}) or a regex. Reports mismatches as BCF / HTML / CSV.

Check every element name in an IFC model against a naming convention. Build the pattern visually or as a regular expression, target it at the classes it applies to, preview the matches before you run, and get back every element whose name doesn't conform.

Naming conventions are agreed at the start of a project and enforced by nobody. Six months in, the model contains three variants of the same wall type, elements named after the family they came from, and a scattering of "Basic Wall 1" that nobody renamed. Every downstream filter, schedule and search that depends on names then produces incomplete answers — and quietly, because a filter that misses half its matches looks exactly like one that found them all.

When to reach for it: When a project mandates a naming convention (corporate BIM standard, BEP, asset register integration, classification system) and you need to find every element that breaks it before sharing the model. Pairs naturally with Bulk Rename — validate first, see which elements need fixing, rename in bulk, validate again.

What you get: An HTML compliance report listing every element that breaks the pattern (class, storey, actual name, expected name or regex), a CSV for pivot tables, and a BCF 2.1 file with one issue per offending element so reviewers can step through them in any BCF-compatible coordination tool.

Example: Assert every IfcWall is named 'EXT-W-{storey}-{index}' before handing the model to QS.

Build the pattern without writing a regex — or with one

Most naming standards are a sequence of fields with separators: a project code, a level, a discipline, a type code, a number. The token builder lets you say that directly — assemble the pattern from parts and it compiles to the expression that gets matched. You don't have to know regular expressions to encode ISO 19650-style naming, which is the reason most naming rules never get automated.

If you do know regex, the builder gets out of the way and you can write the expression yourself. Either way, a live preview shows what the rule currently matches against the real model before you commit to a run — which is what makes an unfamiliar pattern safe to write, because you see it being wrong immediately rather than in a report of four hundred false failures.

Different rules for different elements

One convention rarely covers a whole model. Doors are named one way, walls another, equipment a third. Each rule carries its own targeting — by IFC class, by saved search, or by an explicit selection — so a run can validate several conventions at once and report against each.

Save the whole rule set as a named standard, kept server-side against your account so it follows you between machines and sessions. That's what turns a naming convention from a document nobody re-reads into something re-run on every revision — and as a pipeline step, it runs automatically the moment a new model lands.

From findings to fixes

Findings identify the specific elements and their current names, so the report is actionable rather than a percentage. Bulk Rename IFC Elements is the other half: it applies pattern-based renaming across the model, so the same convention that this tool validates can be enforced rather than just measured.

Reports export as HTML, CSV or BCF — the HTML opens in any browser, which matters when the person who needs to act on the naming is the consultant who authored the model rather than you. Pro accounts can brand the report with a company title and logo.

How to validate IFC element names

Upload your IFC file
Choose Pattern mode: Tokens (build with placeholder chips like {class} or {param:Pset_WallCommon.FireRating}) or Regex (any .NET regular expression — anchor with ^…$ for an exact match)
Enter the pattern your naming standard requires
Optionally restrict the check to specific IFC classes, a saved search, a saved selection, or the current viewer selection
Pick the output formats — HTML, CSV, BCF Issues — then run the tool
Review the results in the BCF tool or hand the .bcfzip off to any BCF-compatible coordination tool

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

How do I check element names against a naming convention?

Build the pattern — visually from tokens, or as a regular expression — target it at the classes it applies to, and run. Every element whose name doesn't match is reported with its current name.

Do I need to know regular expressions?

No. The token builder assembles a pattern from fields and separators — project code, level, discipline, type, number — and compiles it for you. That's the reason most naming standards never get automated, and it's why the builder exists. Regex is available if you prefer it.

Can I test a rule before running it?

Yes — a live preview shows what the rule currently matches against your actual model before you commit. That's what makes an unfamiliar pattern safe to write: you see it being wrong immediately rather than in a report of four hundred false failures.

Can different element types have different naming rules?

Yes. Each rule carries its own targeting — by IFC class, saved search or explicit selection — so one run can validate several conventions at once and report against each.

How do I fix the names it finds?

Bulk Rename IFC Elements applies pattern-based renaming across the model, so the convention this tool validates can be enforced rather than only measured. Save the rule set as a named standard and re-run it on each revision.

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 keeps them 90 days and Team 180 days. Files are never shared with third parties or used to train AI.

Is Validate IFC Element Names free?

Yes. Validate IFC Element Names 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.