A .vtk file is a legacy Visualization Toolkit dataset. It can describe polygonal geometry, structured grids, unstructured meshes or field data in an ASCII or binary record layout.
Private for supported formats — processed in your browser
Convert supported files
Runs on your device
+
Drop VTK files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.
VTK originated with the Visualization Toolkit project in the 1990s and became a foundation of scientific and engineering visualisation. XML-based VTK families later added explicit extensions such as .vtp and .vtu, but the single .vtk legacy form remains common in simulation exports, teaching material and research archives.
How VTK works
The header declares a VTK file version, a comment, ASCII or BINARY encoding, and a dataset type.
POLYDATA stores a POINTS array followed by polygon, line, vertex or strip connectivity.
The POLYGONS header declares both polygon count and total integer count, allowing strict truncation checks.
Scientific scalar and vector attributes can accompany geometry but do not map to simple mesh targets.
When to use VTK
Opening a legacy simulation surface
Moving research geometry into a common mesh viewer
Validating polygon connectivity without a desktop tool
Creating a web or printing rendition from scientific geometry
Strengths and limitations
Strengths
Well established in scientific tooling
ASCII files are straightforward to inspect
Dataset headers expose structure before the payload is read
Limitations
One extension covers several incompatible dataset shapes
Legacy binary files depend on strict byte-order rules
Field data is easily lost in ordinary mesh targets
Compatibility
ParaView, VTK, VisIt, MeshLab and many simulation packages read legacy VTK. Novus Convert supports bounded ASCII POLYDATA points and polygons, checks all declared counts and indices, and exports STL, OBJ, 3MF, GLB, glTF, PLY or USDZ locally. Other dataset types and binary legacy payloads remain explicit limitations.
Polygon geometry is preserved; point fields, cell fields and scientific metadata are not carried into geometry-only targets.