# Import and export

## Export

Any member can export a collection from the Collections panel on the project's page, on any plan, even after a downgrade. There are two formats:

| Button | File | Reads back into Latitude 10 |
| --- | --- | --- |
| **Export** | `<name>.latitude10.collection.json`, our own format, version 1 | Yes |
| **Export for Postman** | `<name>.postman_collection.json`, Postman Collection v2.1 | No |

The Postman file uses the latest version of your document: a `baseUrl` variable, each request's method, path, parameters and body, and Postman's own auth for each operation's security scheme, with empty `{{apiKey}}`, `{{token}}`, `{{username}}` or `{{password}}` variables for you to fill in. A saved request whose operation is gone from the latest version is left out, and the collection's description says how many.

Neither file holds a credential, because a collection never does: see [Secrets](secrets).

## Import

Editors and up import a `latitude10.collection.json` file in the Collections panel, on Pro and up. It becomes a new collection, unpublished. Each value is checked as a save is, the secret check included, and one refused value fails the whole file, with the request and the field named.

| An import of | Answers |
| --- | --- |
| A file over 1 MB | “Imports are at most 1 MB.” |
| A Postman collection | “Postman collections can’t be imported. Export from Latitude 10 instead, or save the requests from Try it.” |
| Any other JSON | That it should be a `latitude10.collection.json` file exported from Latitude 10. |
| A field the format doesn't have | The field, refused. |
| More requests than your plan holds per collection | The plan's number and the file's. |

## Where this comes from

- `app/reference/_lib/collections/exchange.ts`
- `app/reference/_lib/collections/respond.ts`
- `app/reference/_lib/collections/store.ts`
- `app/workspace/actions.ts`