INSITE .eif rebuild online
Packs your edited XML back into an export INSITE will actually import. Runs in your browser against our server — there is nothing to install and no licence to keep alive.
Sending costs nothing. We confirm we have your files, run the job on our server and tell you whether we can do it. You decide about paying after that — and you get a ready-to-use .eif file.
| Price | 120 credits ($120.00) |
| You upload | .xml + .eif / .etf |
| You get back | .eif |
| Max size | 32 MB |
| Applies to | INSITE ECM image · INSITE template (.etf) · CM2350 / CM2250 / CM2150 |
- A ready-to-use .eif file, in seconds
- A yes-or-no answer on your file before you pay anything
- Works from any machine — nothing to install or license
- Charged per file, only when it succeeds
- No copy of your file is kept, ever
| NavKal .zenc decrypt | 250 cr |
| NavKal .zenc rebuild | 250 cr |
| INSITE .eif opener | 120 cr |
How it works
Four steps, and you find out whether it can be done before you pay anything. What you get back is a ready-to-use .eif file.
Upload it here. We confirm on screen that it arrived, with its name and size. This costs nothing.
We run the whole job on our server and answer one question: can we do this file, yes or no. If the answer is no you are told why, and nothing is charged — ever.
Only if the answer was yes. The price is shown before you decide, you tick to accept the payment terms, and the credits come off your balance.
Straight away, in the browser. Your file is processed in memory and never written to our disks.
How you pay
This tool costs 120 credits per file. Credits are prepaid and one credit is one US dollar — 120 credits is $120.00, with no subscription, no monthly fee and no minimum order.
You buy credits with a card or a PayPal account on the credits page, in packs — the larger packs carry a bonus, so a shop doing several files a week pays less per file. Credits do not expire and every movement, spent or returned, is listed in your account. Before any payment goes through — buying credits, or spending them here — you tick a box to accept the payment terms, and they are shown in full at that moment rather than hidden behind a link.
If a job fails after you have paid, the credits go back to your balance automatically and a refund line appears in your history. You are never charged for a file you did not receive.
How the INSITE .eif rebuild works
Making an archive INSITE accepts is not the same as making a valid archive. INSITE's importer wants the exact shape its own exporter writes — the streaming layout, the trailing descriptor with its signature, its own extra fields, its own version marker. A perfectly good ZIP built by anything else is refused with error 10426 and no explanation.
So this tool does not build a container from nothing. It takes your original export apart, keeps everything about the container, and puts your document inside it. What comes back looks to INSITE exactly like something INSITE wrote.
It also renames the entry inside the archive to match the file name you get. That sounds cosmetic and is not: the inner name is the identity INSITE imports by, so a file saved under a new name with the old name still inside makes INSITE offer to REPLACE the original image rather than add this one. Shops lose work that way.
Before you are handed the file it is opened again and the document compared with yours, byte for byte. If they differ you get an error and a refund, not a file — because a container INSITE rejects is a problem you would only discover standing at the truck.
Questions
Because the name inside the archive matched an image already in the database — the file name on disk is not what INSITE goes by. This tool sets the inner name from the file name you get back, so give your XML a distinct name and the rebuilt export imports as a new image.
If the cause is the container, yes — that is what this tool exists for. Error 10426 also appears when the work order or image name duplicates one already in INSITE, and no rebuild can help with that; rename it, or remove the old image first.
Yes, and it has to be the export the XML came from. Its container is what makes the result acceptable to INSITE — that part cannot be reconstructed from the document alone.
No. The file is processed in memory and never written to disk. Nothing is stored, nothing is indexed, and the result only exists in your browser once it comes back. Close the tab and it is gone.
The credits go back to your balance automatically and a refund line appears in your credit history. You are only ever charged for a file you actually received.
No. It runs on our server, so it works from a workshop laptop, a machine in the yard, or a computer that has never had manufacturer software on it. There is no licence, no dongle and nothing to keep alive.