# FAQ - Pruneline 1.x documentation

> Short answers to common questions about Pruneline.

## Does Pruneline delete anything?

Not on its own. The scan only reads. Pruneline changes something only when you ask: **Move to Trash** for a template, pattern, template part or menu with no reference found (you can restore it from the Trash), or deleting leftover data after you have downloaded its export and ticked the confirmation. See [Leftover data and cleanup](leftover-data).

## Which page builders does it read?

Elementor, Beaver Builder, SiteOrigin Page Builder, Bricks, Oxygen, Divi and WPBakery, as well as the block editor. Divi 5 layouts are blocks, so they show on the **Blocks** tab. Saved templates are listed for Elementor, Beaver Builder, Divi, Bricks and Oxygen. See [Page builders and templates](page-builders).

## What does "No reference found" mean?

Nothing Pruneline scanned points at the template or pattern, and it isn't applied by display conditions, popup triggers or as Elementor's site kit. A theme or plugin may still insert it from its code or its settings, which Pruneline can't see. That's why it says "No reference found", not "unused". Check it before you trash it.

## Is my data safe when cleaning up?

Pruneline only offers to delete data it has traced to an inactive or deleted plugin or theme. Data whose owner it can't find, WordPress's own data, and data an active plugin uses are never offered. You download an export of everything that will go before you can delete it, and each item is checked again just before deletion. Database tables are exported as their structure only, so back up your database before deleting a table.

## Does Pruneline slow my site down?

No. Nothing runs for visitors. The scan only runs when you start it on **Tools → Pruneline** or with WP-CLI, plus a quick read of one post each time you save it. In the block editor, administrators' browsers send the list of known blocks at most once a day. The Site Health check runs when you open **Tools → Site Health**.

## Can it tell me about plugins I already deleted?

Yes, if Pruneline read them while they were installed. It keeps what it learned, so **What breaks** and **Leftover data** can still name them. Plugins deleted before Pruneline's first scan can't be named.

## Does it need WooCommerce?

No. It works on any WordPress site. With WooCommerce, products are scanned like pages. Orders aren't scanned.

## Does it audit shortcodes?

Only page builders' own shortcodes, such as Divi 4 and WPBakery modules. For every shortcode on your site, and to hide the ones whose plugin is gone, use Bracketline, our free shortcode audit. With it active, Pruneline's **What breaks** tab counts each plugin's shortcodes too.

## Who can use it?

**Tools → Pruneline** and **Settings → Pruneline** are for administrators.

## What happens to my data if I delete Pruneline?

On **Deactivate**, Pruneline asks what should happen to its data if you then delete it. Keep it (the default) and the scan results are there if you install Pruneline again. Choose **Delete it permanently when the plugin is deleted** to remove its settings and the scan's index. Nothing it reported on is touched. If you deactivate without answering, for example with a bulk action, the data is kept.

## Is it translatable?

Yes. Translate it on translate.wordpress.org, or with Poedit or Loco Translate using `languages/pruneline.pot`.

Source: https://extendiment.com/plugins/pruneline/docs/1.x/faq