> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/gis-quick-hints/qgis-split-multi-field-shapefiles.md).

# QGIS: Split Multi-field Shapefiles

Split a multi-field shapefile into separate field boundary shapefiles in QGIS for GeoPard import.

If one shapefile contains several field polygons, split it before import. GeoPard imports one field boundary per shapefile. This QGIS workflow helps you prepare clean files faster and avoid import issues.

### Before you start

* Make sure the layer has a unique field name or ID.
* Create an empty output folder in advance.
* Remove `/`, `\`, and similar special characters from field names.

### Split a multi-field shapefile in QGIS

#### 1. Open the shapefile in QGIS

Open the source shapefile in QGIS. Confirm it contains multiple field polygons.

<figure><img src="https://lh5.googleusercontent.com/G8ooE_FarMCXvt6CjpvfwgRIiIwLVcSki84FFUiBelII7dZVLJHPN2K_Dj4As-VZNXYsut1q2JGtYEir3GCVfWqwKe4UAI9r9OcIM87jOkDRfiGes_wmD6zTmUyZpUZXgkQBUaW8RCsdaUKY18kaVQ" alt=""><figcaption><p>Initial field boundary layer with multiple polygons.</p></figcaption></figure>

#### 2. Open the split tool

Open the layer options and choose **Split vector layer**.

<figure><img src="https://lh4.googleusercontent.com/g5B3A43gGlRbUBv2hkAt8xVT7UXzLvj06KB99R471uQQAIZLdoHFPmopQfz9ntwflEEN70DDUuMp7LQGqPocfzkBWbVc27Fm3pPCu2kWhbfnaG54TKGKmj4gKJw7sA10NKJf6ezJ62JVLtMlpSAl1Q" alt=""><figcaption><p>Open the split workflow.</p></figcaption></figure>

#### 3. Choose the layer, attribute, and output folder

Set:

1. The layer to split.
2. A unique attribute for each field.
3. The output directory.

<figure><img src="https://lh3.googleusercontent.com/oWwaxwcCPhOp6kIlpDM4z0CK_J_Q6QGCoIdXhr-vMrpQrf_HOLT5ZfHYExEk7J0QIYdPKunOdhe14S9Ay_-FtwGnTnq19GdtnWC4cUcEhEOXIGj7vZdZPsCovszX0sVdz1bF-yraci-5g09ZNJRocw" alt=""><figcaption><p>Select the source layer and split attribute.</p></figcaption></figure>

#### 4. Set the output format

Choose **ESRI Shapefile** as the output format.

<figure><img src="https://lh6.googleusercontent.com/tDOJ7vPBHqCy8peu5Xb97FkYz43HZXnniWwYj6-UXcaMyJaEvuWqx6ew40n9OvXM9OGrPGof0rWasEcgQFjh9SEakNXKW4K4n3Ei56B6jwttr_NW30naaD4OYNJERbQeqeX7bE4JJNd_HwYlgdKIqg" alt=""><figcaption><p>Set the output folder and shapefile format.</p></figcaption></figure>

#### 5. Run the split

Click **Run**. QGIS creates one file per polygon. Each polygon becomes a separate field boundary shapefile.

#### 6. Convert `.gpkg` files to `.shp` if needed

Some QGIS setups create `.gpkg` files first. If that happens, open each file and save it again as **ESRI Shapefile**.

1. Right-click the layer.
2. Select **Export** → **Save Features As**.
3. Choose **ESRI Shapefile**.
4. Set the file name and location.
5. Remove unneeded attributes if needed.

### Result

You now have one shapefile per field. Each file is ready for field boundary upload in GeoPard. This saves setup time and reduces avoidable import rework.

### Related QGIS guides

* [QGIS: Convert CSV to SHP](/geopard-tutorials/gis-quick-hints/qgis-convert-csv-to-shp.md)
* [QGIS: Reproject Shapefile](/geopard-tutorials/gis-quick-hints/qgis-reproject-shapefile.md)


---

# 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.geopard.tech/geopard-tutorials/gis-quick-hints/qgis-split-multi-field-shapefiles.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.