# Delete Fields

Source: https://www.digiparser.com/docs/guides/fields-and-tables/field-setup/delete-fields

Fields & TablesField Setup

# Delete Fields

Remove fields from your parser

Copy MarkdownOpen

# [Delete Fields](#delete-fields)

Feedback

You can **remove** a field or table from your parser when it's no longer needed.

## [How to delete a field or table](#how-to-delete-a-field-or-table)

Feedback

1.  Go to **Settings -> Fields & Tables** (or **Fields & Tables** in the parser sidebar).
2.  Find the field or table you want to remove.
3.  Click the **trash** icon on that field or table.
4.  In the **Delete field?** or **Delete table?** dialog, confirm by clicking **Delete** (or **Cancel** to keep it).
5.  Click **Save Fields**.

app.digiparser.com![Field row with delete button](https://documents.digiparser.com/docs/screenshots/2026-07-23/fields-and-tables-invoice-schema.png?sig=270e4a2eb33805a857cb9a0b464a0e8052eb19822cea58bc38fcac4519ac0733)

## [What happens when you delete a field](#what-happens-when-you-delete-a-field)

Feedback

*   The field is **removed from your parser's schema**. New documents will no longer extract that field.
*   **Existing extracted data** for that field is **not** deleted from already processed documents. It stays in the database, but it may no longer show in the default data table view or in exports unless you explicitly include it.
*   If you **re-process** an existing document after deleting a field, that document's data will follow the new schema (the deleted field will no longer be extracted).

## [When to delete a field](#when-to-delete-a-field)

Feedback

*   You **no longer need** that information (e.g. you stopped tracking "PO Number").
*   You **duplicated** a field by mistake and want to remove the duplicate.
*   You're **simplifying** your parser and removing rarely used fields.

## [Before you delete](#before-you-delete)

Feedback

*   **Check exports and integrations**: If you export to Google Sheets, email, Zapier, or another destination, ensure that flow doesn't depend on this field. Removing it could affect those exports.
*   **Check Post Processing**: If you use Post Processing (e.g. custom code or lookups) that references this field, update that logic first.
*   **Consider disabling instead**: If you might need the field again later, you could **disable AI extraction** instead of deleting. The field stays in the schema but won't be extracted; you can turn it back on later.

## [Next steps](#next-steps)

Feedback

*   [Add/Edit Fields](/docs/guides/fields-and-tables/field-setup/add-edit-fields) - Add or edit fields.
*   [Disable AI Extraction](/docs/guides/fields-and-tables/field-setup/disable-ai-extraction) - Turn off extraction without deleting a field.

How is this guide?

GoodBad

[

Add/Edit Fields

Add and edit fields in your parser

](/docs/guides/fields-and-tables/field-setup/add-edit-fields)[

Field Types Explained

Understand the different field types available

](/docs/guides/fields-and-tables/field-setup/field-types-explained)