

The comment thread: soft bubbles, coloured initials, reaction counts on each bubble and a quiet Like, Reply and time row. Rendered on the server as plain HTML, so it all works with JavaScript turned off.
CommentAura turns the native WordPress comment section into a modern discussion experience, without taking your data hostage.
Everything is stored in wp_comments and wp_commentmeta, exactly where WordPress puts it. Deactivate CommentAura and every comment, every reply, and every permalink still works. That is not a migration path — it is the architecture.
1. Zero lock-in. Your comments are native WordPress comments. No iframe, no external service, no account for your visitors, no export step if you leave. Uninstalling removes CommentAura’s own data and never touches a single comment.
2. It works without JavaScript. The comment thread is rendered on the server, in your page’s HTML. Search engines index it. Readers with slow connections see it. Screen readers read it. Reading, posting, editing, voting and reacting all work as plain form submissions. JavaScript only makes them faster: a half-kilobyte script loads with the page, and the rest — including WordPress’s own React library — loads only when a reader scrolls near the comments. You can switch it off in Settings.
3. No ads, no trackers, no third-party requests. CommentAura sends nothing to anyone. There is no analytics beacon, no CDN call, no “sponsored” content injected into your discussions.
Under CommentAura Import / Export:
wp_comments already, which is where CommentAura reads from. What those plugins keep in their own tables is the material around the comments, so CommentAura brings across the part that would otherwise be lost: subscriber lists and votes. Nothing is deleted from the other plugin, and running it twice does not double anything.Note that Disqus exports produced since 2019 contain no email addresses and no IP addresses for guest commenters. CommentAura preserves the display name, imports with an empty address, and tells you how many were affected rather than letting you find out from a support ticket.
A page with CommentAura active but no comment thread loads zero CommentAura assets. Not a small file — none.
A page with a thread loads about 10 KB (compressed) until a reader reaches the comments. Everything CommentAura itself ships comes to about 19 KB. WordPress’s own React library, which the interactive parts use, loads only when the comments come into view. Reaction faces are small images, about 1 KB each, loaded only when they are shown.
Rendering a thread costs a fixed number of database queries regardless of how many comments a post has, because replies are fetched per level rather than per comment. A post with 10 comments and a post with 10,000 cost the same.
The reaction faces are Fluent Emoji by Microsoft (https://github.com/microsoft/fluentui-emoji), used under the MIT licence. The licence ships with the plugin in assets/reactions/LICENSE.txt. The faces are bundled inside the plugin; nothing is loaded from Microsoft or anyone else.
commentaura/v1assets/src, next to its build in assets/buildThe scripts in assets/build are compiled from assets/src with @wordpress/scripts 30, using the webpack.config.js included in the plugin. To rebuild them, run npm install @wordpress/scripts@30 and then npx wp-scripts build in the plugin folder.
Everything described on this page is free and stays free. A separate paid plugin, CommentAura Pro, sold at https://waafaa.com/product/commentaura/, adds tools for the people who run the discussion: a moderation queue, rules, AI triage and analytics. It is never needed to use anything in this plugin.