What is the OV2 file format?
.ov2 is a binary database file used for storing POI data on TomTom navigation devices. POI (Point of Interest) is a specific point location that may be found useful or interesting - typical POIs include ATMs, train stations, speed cameras, museums and petrol stations. Each POI is represented on the map as a named point with geographic coordinates (longitude and latitude, encoded as signed 32-bit integers × 100,000 in WGS84) and optional information. Users can load public POI databases onto their devices as well as create custom POI entries.
.ov2 files can store custom POI databases created by users. Custom POI entries can have a unique icon associated with them via a companion .bmp file of the same base name - for example, speedcams.ov2 paired with speedcams.bmp. Databases can be synchronized across devices using applications that support the format. Navigation devices typically use their own file formats for POI data, but many conversion tools are available to facilitate database transfers from GPX and other standards.
TomTom HOME management software was the primary desktop tool for syncing .ov2 files to devices. Although TomTom's current GO models have mostly transitioned to live subscription-based services, .ov2 custom POI remains supported on older hardware and some current devices.
Security & safety
RISK: LOWOV2 files are plain binary data records with no executable content and no scripting capability. They are safe to load onto a TomTom device. The main practical risk is data quality: commercially distributed speed camera databases may be outdated or inaccurate - verify the source and date of any POI database before relying on it for navigation. Avoid download sites bundling adware with 'free POI files'; prefer reputable GPS community databases (PocketGPSWorld, POI Factory, etc.).
Format details
in a nutshellPrograms that open OV2 files
Technical details
deep spec| Developer | TomTom N.V. |
| Encoding | Binary, little-endian |
| Container | Flat binary record sequence; no file header or container wrapper |
| Record structure | 1-byte type + 4-byte record length + 4-byte longitude + 4-byte latitude + null-terminated ASCII name |
| Coordinate encoding | WGS84 degrees × 100,000 as signed int32 (longitude ±18,000,000; latitude ±9,000,000) |
| Icon companion file | Same-name .bmp file provides the POI map icon (e.g. speedcams.bmp alongside speedcams.ov2) |
| Typical file size | A few KB to a few MB; minimum ~13 bytes per simple POI record |
| Record type codes | 0x02 = simple POI, 0x01 = deleted/skipper record, 0x00 = end marker |
| Platform | Windows/macOS (TomTom HOME); TomTom GPS device firmware |
| Format status | Frozen; well-documented by the TomTom community despite being proprietary |
| Typical use cases | Speed cameras, petrol stations, parking, custom navigation waypoints |
| Released | Early 2000s with TomTom Navigator; widely used with TomTom GO devices throughout 2000s-2010s |
| Latest version | Format frozen; TomTom GO devices have transitioned to live services but OV2 still supported on older hardware |
| Specification | gordthompson.github.io |
OV2 conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about OV2 files.