> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/software/freefly-flow.md).

# Freefly Flow

Freefly Flow is Freefly's iPad app for processing and visualizing LiDAR data. Process scans in the field, explore point clouds, and export industry-standard formats.

## Download

Freefly Flow is available on the App Store for iPad.

{% hint style="info" %}
**System Requirements**

* iPad with iPadOS 18 or later
* App version 3.0 or later recommended
  {% endhint %}

## Key Features

* **Project Management** - Create and organize LiDAR projects with over 6,500 coordinate reference systems supported
* **GNSS Post-Processing** - PPK processing with base station correction data
* **Point Cloud Visualization** - Explore billions of points with gesture-based navigation
* **Export Options** - Export to LAS or compressed LAZ formats with configurable point density

## Usage with Flux LiDAR

Freefly Flow is the companion app for processing data from Flux LiDAR sensors. For detailed workflows including mission planning, data capture, and processing tutorials, see:

{% content-ref url="/pages/iZ39a8FHy2m0Je8lRjyG" %}
[Data Capture Workflow with Flux](/ecosystem/payloads/flux-lidar/mapping-workflow-with-flux.md)
{% endcontent-ref %}


---

# 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.freeflysystems.com/ecosystem/software/freefly-flow.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.