Current data format

Understanding .asmaps and .asmaps.backup

MapTools uses database-backed storage for large projects. A project file and an app backup serve different purposes and cannot be used interchangeably.

Two formats, two purposes

Both extensions belong to MapTools, but the current versions contain different database packages.

.asmaps — Portable project (.asmaps)

An .asmaps file contains exactly one editable MapTools project. The version 1 ZIP container packages a manifest, the portable SQLite exchange database project/project.sqlite, SHA-256 checksums and optional project assets. Coordinates are stored in WGS84 (EPSG:4326).

.asmaps is intended for project exchange and preserves MapTools objects, geometry, collections, import records, alarms, search grids and supported assets. Format v1 is not password-encrypted; credentials, API keys and tokens are excluded.

.asmaps.backup — App backup (.asmaps.backup)

An .asmaps.backup file is a restore backup of selected app areas. It may contain the project catalogue, several internal Room/SQLite project databases with assets and, depending on selection, settings, profiles, maps, layers, POI data, terrain data and map styles.

.asmaps.backup is not a single-project exchange format. Backups can be password-protected and are fully analysed, limited and checksum-validated before restore. An encrypted backup cannot be restored without its password.

Which format should you use?

Continue working in MapTools

.asmaps for one project when MapTools structure and editability should be retained.

Device move or restore

.asmaps.backup for selected or extensive app areas; store the password securely and separately from the backup file.

Integrity and privacy

Checksums detect damaged or modified content but do not prove its origin. Open files only from trusted sources. Projects and backups can contain sensitive location, track and note data.