How it works
- Export the project from the vendor's software on the engineering PC — exact steps for each vendor are below. Every supported input is an open, vendor-produced export: XML, YAML, text or CSV.
- Drop the file above. Parsing happens in your browser via WebAssembly — on first use it fetches the ~10 MB engine, then works even offline.
- Review the screens. Every screen lists its buttons, indicators and value displays with their real tag names. Untick screens you don't need, retype or delete elements, fix labels.
- Download the profile and open it in the free LineKeeper app (iOS / Android). The app connects to the PLC over EtherNet/IP, Modbus TCP or S7 and your line has a screen again.
What you get — and what you don't. The converter rebuilds the operator controls: buttons, switches, indicators, numeric displays and inputs, with the tags they really read and write. It does not reproduce layout graphics, pictures or animations — the result is a clean, phone-friendly panel, not a pixel copy of the old screen.
How to produce the export, per vendor
Rockwell FactoryTalk View ME / SE (PanelView Plus)
In FactoryTalk View Studio: open the project, right-click Displays →
Import and Export… → Export graphic information from displays. You get one
XML file per display; zip the folder and drop the zip here. A .mer
runtime alone cannot be converted — it is a compiled file. If you only have the
.mer and replacement panel hardware, Rockwell's free ME Transfer
Utility loads it onto the new panel as-is.
Rockwell Studio 5000 View Designer (PanelView 5000)
View Designer v9 and later: File → Export project produces a folder with
ViewApplication.hmi plus one .hmi file
per screen. Zip that folder and drop it here. A single screen's
.hmi works too.
Rockwell FactoryTalk Optix
No export needed — an Optix project is already plain YAML on disk. Zip the project
folder (the one containing Nodes/ and the
.optix file) and drop the zip.
Siemens TIA Portal — WinCC Comfort, Advanced, Unified
Use the TIA Portal Openness export for the HMI device: one SimaticML
.xml per screen, plus the HMI tag tables (and discrete alarms if
configured). Drop a single screen XML, or zip the whole export folder. Works across TIA
versions — V15 through V20 exports parse the same way.
Weintek EasyBuilder Pro
EBPro v6.10.02 and later: export windows to XML (window export command), one file per
window or a folder — zip a folder. Compiled .emtp /
.exob files are not supported; the XML export is.
Tag & cross-reference CSV — six more vendors through one door
- Pro-face GP-Pro EX: Project → Utility → Cross Reference → save as CSV.
- Mitsubishi GT Designer3 (GOT): Data Browser → export CSV.
- AVEVA / Wonderware InTouch: Application Manager → DBDump.
- Schneider Vijeo Designer: variable export as text/CSV.
- Red Lion Crimson: export the tag database to CSV from the Tags editor. Tags mapped to a PLC address come through; internal calculated tags are skipped automatically.
- Omron Sysmac Studio (NA panels): open the HMI global variable table, select all rows, copy, paste into a spreadsheet and save as CSV. Variable names are the tags.
Column headers are matched by meaning (screen / address / type / comment), so most tag-list CSVs work even when the exact column names differ.
Why this beats rebuilding by hand
A machine's PLC program holds thousands of tags; the dead panel used a few hundred of them. The project export is the filter: it tells you exactly which tags the operator actually needs, what each one was called on screen, and whether it was a button, an indicator or a setpoint. That is hours of tag hunting you don't do at 2 a.m.