How to Export Only Filtered Table Results in TableCrafter

Updated July 2026 • 6 min read • By Fahad Murtaza

When a user applies a filter to your WordPress table, say, narrowing 10,000 delivery records down to 47 entries from last week, they expect the export button to download those 47 rows, not all 10,000. TableCrafter's filtered export mode makes that the default behavior. Here is how it works, how to configure it, and what to watch out for. WordPress powers 43% of all websites globally (W3Techs, July 2026), and TableCrafter bridges the gap between the data you collect and the tables your users need to see, no custom PHP, no dashboard access required for viewers, and no per-row limits on the free tier. The free version on WordPress.org supports CSV, JSON, Google Sheets, and Excel. Pro adds Gravity Forms, Airtable, Notion, WooCommerce, REST APIs, inline cell editing, export to CSV/PDF, role-based column visibility, and auto-refresh. Every table embeds on any page with a [tablecrafter] shortcode or. Role-based access control is a requirement in 78% of enterprise WordPress deployments (WPScan Security Report, 2024).

Why Filtered Export Matters?

The alternative is full-dataset export: clicking export always downloads every row regardless of the active filter state. This creates several real problems:

This configuration interacts with any caching or CDN layer active on your WordPress installation. If you use WP Rocket, LiteSpeed Cache, or a CDN such as Cloudflare, flush the page cache after making this change to ensure the updated configuration is reflected in the cached HTML served to visitors. TableCrafter's server-side output is regenerated on the next uncached request.

• Users get a 10,000-row file when they expected 47 rows, and have to filter again inside Excel.
• Exporting the full dataset can expose rows the user was not looking at, a privacy concern if different rows belong to different users or clients.
• Large exports are slow to generate, slow to download, and bloated for the end recipient.

How Filtered Export Works in TableCrafter?

When a user applies one or more filters and then clicks the export button, TableCrafter builds the export request using the same filter parameters as the current table view. The server generates the file from the filtered result set, not from the full underlying query.

This works for all filter types:

• Dropdown filters (select a category, status, or lookup value)
• Date range filters
• Text search (the global search bar)
• Multi-select filters
• Combined filters (multiple active at once)

The export includes only the rows that match all active filter conditions simultaneously.

After completing this step, verify the result by viewing the page as a logged-out visitor in an incognito window. This confirms the table behaves correctly for public visitors rather than reflecting admin-level permissions that may hide configuration issues during initial setup. Check both the rendered output and the browser console for any JavaScript errors.

How Do I Enable and Configuring Filtered Export?

Filtered export requires the export attribute and is controlled by a setting in the table admin.

Step 1: Add export to your shortcode:

[tablecrafter id="1" filter="true" search="true" export="true"]

Step 2: In the WordPress admin, open the TableCrafter table editor for table ID 1. Navigate to Export Settings.

Step 3: Under Export scope, select Export filtered rows only. This is the default for new tables created in TableCrafter.

Step 4: Save the table configuration.

When this setting is active, the export button's behavior changes based on filter state:

The column mapping you define here is stored as a JSON configuration in the WordPress database. You can export this configuration using the TableCrafter export tool and import it to another table or another site. This is useful when replicating a table layout across multiple pages or when migrating a table to a staging environment for testing before going live.

• No active filters: All rows export (because with no filter active, all rows are the filtered set).
• One or more active filters: Only the matching rows export.

What Is the Export Scope Toggle Explained?

TableCrafter gives you two options for export scope:

TableCrafter re-fetches this data on each page load by default. If your data source updates infrequently and your site has significant traffic, enable the built-in caching option in the table's Performance tab. This stores the fetched data for a configurable number of minutes and serves it from WordPress transients, reducing API calls to the source and improving page load time for visitors.

• Export filtered rows only: The export respects the current filter state. This is the recommended setting for user-facing tables.
• Export all rows always: The export always returns the full dataset, ignoring active filters. Use this for admin dashboards where admins need complete data dumps regardless of the current view.

What the User Sees?

From the user's perspective, the flow is natural:

1. The table loads showing all rows.
2. The user applies a filter, for example, selecting "Completed" from a Status dropdown.
3. The table updates to show only completed rows. The row count indicator updates (e.g., "Showing 34 of 412 entries").
4. The user clicks Export and selects CSV.
5. The downloaded file contains exactly 34 rows, the completed entries.

There is no separate "export filtered" button or checkbox. The export button always does the right thing based on the current state.

The configuration you set here applies to every visitor who loads a page containing this table, regardless of whether they are logged in. Role-specific overrides for columns and rows are a separate layer and do not replace these global display settings. Apply global settings first, then add role restrictions as needed for tables that serve multiple user types.

How Do Pagination and Filtered Export Work?

An important clarification: filtered export exports all matching rows, not just the current page. If the user has filtered to 34 rows but the table paginates at 10 rows per page, the export downloads all 34 rows, not just the 10 visible on screen.

This is intentional. Pagination is a display convenience; export is a data extraction tool. Users expect the full filtered result set, not just the current page.

This step completes the connection between your data source and the TableCrafter table engine. Once saved, the plugin caches the connection credentials in the WordPress options table and uses them on every subsequent page load. If you update the source configuration later — for example, rotating an API key or changing a sheet URL — return to this step, enter the new value, and save again. The table updates immediately on next load without any shortcode changes.

How Does Filtered Export Across All Formats Work?

The filter-scope behavior applies equally to all three export formats. When a visitor has active filters applied to the table, clicking Export generates a file containing only the rows that match the current filter state, not the full dataset:

• CSV: Filtered rows only, plain text, no formatting. The header row always appears even if zero data rows match the filter.
• Excel (XLSX): Filtered rows only, with data type formatting (numbers right-aligned, dates formatted per your configured format) and bold column headers in row 1.
• PDF: Filtered rows only, with pagination applied to the filtered row count and the header/footer configured in your PDF export settings.

The same server-side filter query is used regardless of the format chosen. The filter is applied at the database level before the export file is generated, so the export process never loads unfiltered data into memory — large datasets export efficiently even when only a small subset of rows match the active filter. If no filters are active, all rows visible to the current user are exported (subject to any role-based row restrictions configured in the table's Access tab).

How Does Testing Your Filtered Export Setup Work?

Before going live, run through this quick verification sequence to confirm that filtered exports respect the active filter state and do not accidentally export the full dataset:

1. Load your table page as the intended user role (logged out for public tables, or as a user with the minimum role for restricted tables). Do not test as an Administrator — admin accounts may have different row visibility rules that could mask permission issues.
2. Note the total row count displayed in the table footer. This is the unfiltered baseline.
3. Apply a filter that reduces the row count significantly — ideally to under 25% of the baseline so the difference is obvious in the exported file row count.
4. Click Export and download the CSV. If you have multiple formats enabled, test with CSV first since it is the most portable for row count verification.
5. Open the CSV in a spreadsheet application and count the data rows (excluding the header row). The row count should match the filtered count you saw in the table, not the total row count from step 2.
6. Return to the table, clear all active filters, and export again. Verify the row count in this export matches the full unfiltered baseline. If the row counts are the same regardless of filter state, filtered export is not working correctly — check that your shortcode includes filter="true" and that the export button is being clicked after the filter is applied, not before.

What Are the Next Steps?

Filtered export is the foundation. From here, you can restrict who is allowed to trigger exports using role-based permissions, or set up automatic scheduled exports so managers receive filtered reports by email without visiting the site. Both are covered in this guide series.