Open your existing hydraulic models in epanet-js

Import models from InfoWater Pro, WaterCAD, WaterGEMS, and InfoWorks WS Pro directly into a lightweight browser workspace. Keep your operational scenarios, asset attributes, and calibration data fully intact.

Imported hydraulic network aligned with a satellite basemap using the epanet-js projection finder.

Preserve your engineering investment across platforms

Distribution models represent years of engineering effort, field calibration, and institutional knowledge. Yet most of these models remain locked inside proprietary vendor containers. When an expensive annual license lapses, or when a consultant delivers a format your team cannot open, accessing that engineering data becomes an unnecessary obstacle.

epanet-js removes proprietary gatekeeping by opening commercial models directly. Network geometry, operational scenarios, and custom attributes import cleanly, run on the standard EPANET 2.3 engine, and are automatically verified against stored simulation results. Whether you are reviewing an inherited file or evaluating alternatives to legacy subscriptions, your model remains completely accessible.

Direct import with scenarios and custom attributes

Traditionally, moving a model out of InfoWater Pro, WaterCAD, WaterGEMS, or InfoWorks WS Pro meant exporting a bare-bones .inp file. That workaround strips critical project data—including scenario hierarchies, customer billing associations, and custom GIS attributes—leaving you to reconstruct the model manually.

epanet-js reads native commercial formats directly. Opening a model brings over its full scenario tree and asset attributes, allowing you to pick up work immediately in a modern, responsive workspace.

Because interoperability works both ways, you can use epanet-js for daily analysis while maintaining compatibility with legacy client mandates. Learn how epanet-js compares directly with InfoWater Pro, WaterCAD & WaterGEMS, and InfoWorks WS Pro.

Scenario management panel in epanet-js displaying operational alternatives and comparative head loss plots.

Automated audit and result verification

Opening an unfamiliar or inherited network shouldn't require manual file audits. Upon import, epanet-js generates a structured diagnostic report detailing asset counts, pipe connectivity, demand allocations, and complex control rules that warrant engineering review.

epanet-js then simulates the network and compares the computed heads and flows directly against the run results stored in the source file. Discrepancies are highlighted on the map immediately, giving you verified confidence in model parity before you proceed with scenario evaluations.

Georeference models onto real-world basemaps

Commercial packages often embed coordinate system metadata, but legacy EPANET .inp files frequently rely on arbitrary CAD grids or local coordinates without defined projections. Historically, aligning these models required manual reprojection in external GIS tools.

The epanet-js Projection Finder streamlines georeferencing during import. Search by EPSG code, projection name, or the municipality the network serves, and choose from candidate projections to seat the network accurately on satellite and street basemaps. The software projects the visual overlay cleanly without altering the model's native coordinate definitions.

Full EPANET .inp compatibility and open storage

The industry relies on .inp as its universal interchange standard. epanet-js runs an unmodified EPANET 2.3 toolkit (v2.3.5), ensuring complete numerical and behavioral parity with official EPA releases—the same friction calculations, pressure formulations, and solver outputs.

For broader project needs, projects save in the open .ejsdb format. This format preserves modern assets that fall outside the standard .inp schema—such as individual customer meter points, DMA boundaries, and scenario definitions—allowing your project to grow without sacrificing compatibility.

The epanet-js open project architecture, maintaining .inp compatibility while preserving advanced spatial layers.

Round-trip interoperability and data export

A flexible modeling tool should never create a walled garden. Everything created or edited in epanet-js exports cleanly: save models back to standard .inp, export network assets to Shapefile, GeoJSON, CSV, or XLSX, and pull time-series simulation outputs directly into spreadsheets for engineering reports.

When contract specifications mandate a deliverable in a specific legacy software, our documented round-trip export guides make handoffs simple. You can conduct your builds, calibrations, and scenario evaluations quickly in epanet-js, then package the final model for client sign-off in InfoWater Pro, WaterCAD, or InfoWorks WS Pro.

Key capabilities of model import

Direct commercial model import

Open native files from InfoWater Pro, WaterCAD, WaterGEMS, and InfoWorks WS Pro with scenarios and custom attributes intact.

Automated result verification

epanet-js simulates the imported network on the EPANET 2.3 engine and benchmarks the results directly against stored run data to verify parity.

Instant georeferencing

The built-in projection finder aligns models using local or unknown coordinate systems to the real-world basemap in seconds.

Complete export flexibility

Export networks and simulation results to standard .inp, GeoJSON, CSV, Shapefile, or XLSX whenever you need to share data with other teams.

Test your existing model in epanet-js

Open your model on our free tier to verify its geometry and simulation results on a modern basemap, or book a demo to discuss team migration workflows.

Put your imported network to work

Once imported, your model is immediately ready for analysis. Conduct extended period simulations, evaluate operational scenarios, test fire flow capacity, run water quality simulations, or allocate customer meter points for comprehensive demand analysis.

Explore related solutions

See what else you can do once your network is loaded.

Frequently asked questions

Frequently asked questions about importing hydraulic models into epanet-js.

How do I import a model from InfoWater, WaterCAD, or InfoWorks?
Select your native project file and open it directly in epanet-js. The importer parses network topology, operational scenarios, and custom metadata without requiring an intermediate .inp export. Once loaded, simulated results are automatically benchmarked against the run data stored in the source file. Read our detailed platform guides for InfoWater Pro, WaterCAD / WaterGEMS, and InfoWorks WS Pro.
What file formats does epanet-js support?
epanet-js natively opens commercial project files from InfoWater Pro, WaterCAD, WaterGEMS, and InfoWorks WS Pro, standard EPANET .inp files, and epanet-js .ejsdb project files. If you are working with an unlisted format or a legacy export, contact our engineering team—we can help translate your legacy network files and recover custom metadata.
How does epanet-js ensure the imported model matches the original?
epanet-js generates an import audit report cataloging all ingested pipes, nodes, patterns, and operational rules. It then executes an automated validation run on the EPANET 2.3 engine, comparing simulated heads, pressures, and flows against the results saved in the source model to highlight any discrepancies immediately.
What is the difference between model import and GIS import?
Model import brings in a complete, pre-configured hydraulic model—including defined demands, diurnal patterns, control rules, and boundary conditions. GIS import builds a new model from raw spatial layers (such as water main Shapefiles or CAD drawings) and assigns topology from scratch. If you are starting from raw GIS layers, visit our model building page.
What does the .ejsdb format store that .inp cannot?
The standard .inp specification is strictly limited to hydraulic elements. epanet-js uses the open .ejsdb format to store modern project data that .inp has no schema for—such as individual customer meter points, DMA polygon boundaries, background layer configurations, and multi-scenario metadata. You can save to .ejsdb for full-fidelity project storage or export to standard .inp at any time for interchange.
What if an older model lacks real-world GIS coordinates?
You can still import and display it accurately. When a model uses local grid coordinates or an unspecified projection, the built-in Projection Finder helps you identify the correct coordinate reference system. You can search by EPSG code, projection name, or service area location to align the model onto satellite basemaps without modifying the original CAD or survey coordinates.
Does my model data remain private?
Yes. epanet-js is engineered local-first: all model parsing, simulation, and project storage execute directly within your browser on your local device. No model geometry, customer attributes, or operational records are uploaded to external servers. See our security documentation for technical details.

Modern hydraulic modeling without format lock-in

Open your commercial model in seconds and experience local-first speed with full export flexibility. Launch epanet-js or schedule a technical walk-through.