> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/salesforce/forms/import-export.md).

# Importing & exporting data from PDF forms

Learn how to import and export form data and annotations using XFDF data. Discover the XFDF file format and how to manage field values and widget appearances efficiently. Click to explore more! Salesf

Form data can be saved and loaded the same way as annotations through XFDF data.

![](https://306473577-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfmJo9lQOEYOFBgOyFp26%2Fuploads%2Fgit-blob-2bd991f210e766abadcf3b63057457ac0bd855d1%2Fbde90e8fdc00fd7e47dba8bec2559686e755c173-760x477.png?alt=media)

Please see [import/export annotations](/web/annotation/import-export.md) to learn more.

All of the form field data (field values and widget appearances) is included inside XFDF, for example when calling [annotManager.exportAnnotations](https://sdk.apryse.com/api/web/Core.AnnotationManager.html#exportAnnotations__anchor).

## Learn more

[A short introduction to XFDF file format](/web/annotation/xfdf.md) An introduction to XFDF file format

[Importing and exporting annotations](/web/annotation/import-export.md) To import and export annotation and forms data through XFDF data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/salesforce/forms/import-export.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
