// blog
How to Open a TVW Boardview File in Your Browser, With Nothing to Install
Open the free board viewer and drop the .tvw file on it. It’s read in your browser and never uploaded. You get both sides of the board, every part and pin, the nets and the board’s real edge. The factory tester’s probe points show as test pads. Lenovo and Gigabyte files both open. Copper layers aren’t drawn yet.

A repair tech emailed us last week with a short request: please add TVW. Their board wouldn’t open in our free board viewer, and the viewer had told them why. Now it does open. Here’s what TVW is, what you get, and how the reader was built.
What a TVW file is
TVW is the format of Tebo-ICT View, software made for in-circuit testing, where a fixture of spring-loaded pins presses on a board to test it. Repair people meet it because many laptop boards, often Lenovo and LCFC designs, circulate as .tvw files.
Gigabyte uses it too, for graphics cards and motherboards, in a slightly older version of the format.
It’s a binary format with no public description. Unlike some boardview formats it isn’t encrypted, so no key is needed.
How to open one
- Open the board viewer.
- Drop the .tvw file on it, or press Open board. A ZIP with the .tvw inside works too.
- Add the schematic PDF if you have it, and the two link both ways.
The file is read in your browser tab and never uploaded. Close the tab and it’s gone.
What you get
- Both sides of the board, every part with its pins
- Every pin’s net, so clicking a pin lights the whole net up
- The board’s real edge, with its notches and cut-outs. Lenovo files store it. Gigabyte’s don’t, so the viewer traces it from the copper planes, which are poured almost up to the edge
- Connectors with pins on both faces, such as a graphics card’s edge fingers, with each pin on its own side
- The tester’s probe points as test pads. A TVW file lists each probe point as its own little part, often named like TB_TP123, and a board can have hundreds of them. As parts they’d swamp the parts list. As test pads they stay on the board and can still be found by net, which is handy when you’re looking for somewhere to probe.
We checked the reader on real board files. On one we compared side by side, the part and pin counts matched another boardview viewer’s exactly.
What doesn’t work yet
- Copper. Traces, planes and inner layers are in the file, and the reader walks through them, but the viewer doesn’t draw them yet. You get parts, pins, nets and the edge, as with other formats.
If a file is a version we haven’t seen, the viewer says which version instead of showing a vague error. If your TVW file fails, the viewer checks why in your browser, and asks whether you’d send it so we can fix the reader. Nothing goes unless you press Send.
How it was built
We didn’t start from scratch. Pavel Kovalenko worked the format out years ago in eagleview, released under the MIT license. Our reader is a TypeScript port of his, with fixes from an open OpenBoardView pull request and its review. The most important fix: the file’s header holds two more short text fields than eagleview expected, and when they’re filled in, every number after them was read from the wrong place.
A TVW file has no table of contents. It’s one long stream, so to reach the parts you read everything before them: every layer, every copper shape, the test probes and the fixtures. A pin doesn’t even name its net. It points to a pad on its layer, and the pad names the net.
Because the reader reads files from strangers, it checks every count against the bytes left in the file before using it. A cut-off download is refused cleanly. So is a file built to claim billions of items, which fails at once instead of hanging your browser.
The Gigabyte file a visitor sent
The first version of this reader stopped on Gigabyte files with “a version this viewer can’t read yet”. Then someone’s Gigabyte graphics card file failed in the viewer, and they pressed Send. That one file showed what was wrong, and only one difference was really about the version:
- Counts that looked like constants. In three places, eagleview reads a fixed value where the file holds a count: the points in a probe’s outline, a list of test names, and a part’s second group of pins. Lenovo files always hold the same small value there, so the guess held. Gigabyte’s don’t.
- Data that’s only sometimes there. A fixture setting can come without its data. Lenovo files always include it.
- One real version difference. One block of settings is 2 bytes shorter in Gigabyte’s version.
- A part on both faces. That second group of pins is how a card-edge connector keeps its top fingers and its bottom fingers apart.
With those fixed, the file opens with every part and pin and every pin’s net, and the Lenovo files still read exactly as before. Pressing Send is what made it possible. Thank you, whoever you are.
Thanks to Pavel for the original work, and to the people who reviewed the pull request.
































































































































