Powerful Table, Form & Mail Automations. Form Entry Management (+ frontend table ), integrate with MailChimp, G Sheets, CF7, WPForms, Elementor, etc.
As of April 2026, Tablesome Table is a WordPress email plugin with 8.0K+ active installations and a 4.8/5 rating from 85 reviews. It has been downloaded 375K+ times in total. Requires WordPress 6.7+ and PHP 7.0+. Available on WordPress.org since 2020. Actively maintained — updated within the last month. Downloads are up 436% this week. Support resolution rate: 38%. Top alternative: WP Mail SMTP by WPForms – The Most….
Demo | Docs | Get Pro | Test Beta |Get Support | Submit Feature Requests
= 🎉 New Feature: Frontend Access Control with Email Column Option (Pro) 🎉=
You can now control frontend table access using email columns! This powerful feature allows you to restrict who can view and edit table data based on their email address. Perfect for creating personalized user experiences and managing access to sensitive information directly from your tables.
With Tablesome you can save contact form submissions, redirect after form submit, create responsive data tables, import and export tables & entries as CSV & XLSX files, and automatically export data to Mailchimp, Notion, etc.
You can create post tables &…
This is an easy-to-use plugin with excellent functionality and good support. Thanks!
Subject: Critical Memory Usage and SQL Redundancy Issue with Tablesome Plugin
Message:
Hello Tablesome Support Team,
I would like to request your assistance regarding a serious issue affecting the Tablesome plugin.
Error Message:
When deleting or modifying data and then clicking “Update,” the following error occurs:
SyntaxError: Unexpected token '<', "
This causes the backend update feature to become unusable.
In addition, I have identified a more severe problem related to memory usage.
When updating records in the admin dashboard, the plugin loads all 19,000+ rows into memory at once.
This behavior leads to Out of Memory (OOM) errors and 502 Bad Gateway crashes.
Details:
When memory usage reaches around 7GB, the server’s OOM Killer terminates the Apache process,
even though the actual table size is only about 5MB.
This happens every time an update operation is performed, even for small edits.
It appears that the plugin does not use pagination or batch-loading when processing updates.
Additional Log Findings:
From the latest error logs, it seems that the plugin repeatedly calls the
convert_conditions_to_sql_string() function for the same condition
(author_id = current_user_id()), generating redundant SQL operations
and significantly increasing memory usage.
Request:
Could you please review whether it’s possible to implement pagination, query caching,
or other optimization methods during backend filtering or shortcode rendering
to prevent redundant SQL calls and excessive memory loading?
Thank you very much for your time and assistance.
Best regards
great easy to use and good
The free version is quite easy to use and provides easy integration with elementor forms.
I was using another well known plugin which was not easy to use even in its paid version. I changed for Tablesome, no regret at all, so far so good.
some Forminator’s entries, works well
| WordPress | 6.7+ requiredTested up to 6.9.4 |
| PHP | 7.0+ required |
Fix: Forminator signature field not captured in table (showing “Array” instead of URL)
Fix: General fixes
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.