Short answer: DataViews is the interface component that replaced WordPress's old plain list tables on the Posts, Pages, and Media screens, starting in WordPress 7.0 (released 2026-05-20). Instead of one fixed table, DataViews lets you choose between a table, a grid, or a list layout for the same content, filter and sort it inline without the page reloading, adjust how dense the rows or cards are, and select items for bulk actions directly in the same view. If your Posts screen suddenly looks like a wall of cards instead of a plain list of rows, you're looking at DataViews' grid layout, and it's one setting away from looking like the old table again, which the plain-list guide covers step by step.
What DataViews actually is
DataViews isn't a plugin, a theme feature, or something you installed. It's a component WordPress core itself uses to display any collection of items, posts, pages, media files, and more, in a consistent, configurable way. It first appeared inside the Site Editor for managing templates and patterns, was expanded in later releases, and in WordPress 7.0 it became the technology behind the Posts, Pages, and Media screens that almost every site owner touches daily. That's the reason it feels so sudden: the change happened at once, on the screens with the highest traffic in the entire admin.
Think of it less as "a new screen" and more as "a new kind of screen that several parts of WordPress now share." Once you understand how it works on Posts, the same logic applies wherever else you encounter it.
The three layouts, and why yours might look unfamiliar
DataViews offers three ways to display the same underlying list:
- Table: rows and columns, the closest match to the classic list table you're used to.
- Grid: card-style tiles, useful for content with a strong visual element like Media, and the layout most likely to surprise someone expecting the old table.
- List: a compact row-based layout that sits between table and grid, with its own adjustable density.
Within table and list layouts, WordPress also supports a density setting (compact, balanced, or comfortable), which controls how much vertical space each row takes. None of the three layouts is "more correct" than another; they're the same posts shown differently, and switching between them doesn't change, hide, or delete any content.
What's the same as before
It's worth being explicit about what didn't change, because the redesign gets blamed for more than it actually did:
- You can still filter by status, author, category, and date.
- You can still sort by any visible column.
- You can still select multiple items and apply a bulk action, like moving several posts to trash or changing their category at once.
- Every post, page, and media file that existed before the update is still there, untouched. DataViews is a display layer, not a data migration.
What's genuinely different
The functional changes, not just the cosmetic ones, are:
- Filtering and sorting happen inline, without a full page reload, so trying three different filter combinations in a row is noticeably faster than the old table.
- You can combine filters rather than applying one at a time, which matters most once you're managing more than a couple dozen posts.
- The layout and density are your choice, saved per screen, rather than a single fixed table everyone sees the same way.
- Bulk actions apply to whatever you've filtered down to, so you select from a narrowed list instead of hunting through the full one, covered in more depth in the bulk-editing guide.
The mental model that actually makes this click
Here's the reframe most explanations skip: stop thinking of the Posts screen as "a page that lists your posts" and start thinking of it as "a saved view of your posts, configured the way you want it." That's a small shift, but it explains almost every point of confusion people run into.
It explains why the screen can look completely different for two site owners on the same WordPress version: one picked grid layout, comfortable density, filtered to their own posts; the other picked table layout, compact density, filtered to drafts only. Neither is broken. It explains why switching layouts doesn't feel like "resetting" anything: you're not changing a setting buried in a settings page, you're just choosing which lens to look at the same data through. And it explains why a screenshot in an older tutorial might not match your screen even on the identical WordPress version, if the tutorial's author had chosen a different layout or density than you have.
Once you treat the view as configurable rather than fixed, the instinct to hunt for "where did the real list go" mostly disappears, because there isn't a hidden "real" version underneath; the view you're looking at is the real one.
Where you'll run into DataViews next
The command palette can jump you straight into a filtered DataViews view, for example searching a post title takes you directly to that post rather than making you scroll a list to find it. And the settings translation table in where did WordPress settings move covers the handful of things that changed location alongside DataViews, in case the confusion isn't limited to this one screen. For the complete list of everyday tasks in the redesigned admin, the full admin walkthrough is the place to start.
FAQ
Is DataViews a plugin I need to install? No. It's built into WordPress core as of version 7.0 for the Posts, Pages, and Media screens. There is nothing to install, activate, or update separately.
Did DataViews change how my existing posts and pages are stored? No. It only changes how the list is displayed and interacted with. The underlying content and data are unaffected.
Why does my Posts screen look like cards while a colleague's looks like a table? You're most likely looking at different layout choices (grid versus table), which DataViews remembers per screen and per person. Both are valid views of the same content.
Can plugins that add custom columns to my Posts screen break under DataViews? A plugin that adds columns, filters, or bulk actions to the Posts or Pages screen may need its own update to render correctly under DataViews. If a plugin's custom column has disappeared since updating to WordPress 7.0, check whether that plugin has shipped an update since the release.
Does DataViews slow down the Posts screen on a site with a lot of content? It's designed to filter and sort without full page reloads, which tends to feel faster in day-to-day use, though performance on very large content libraries depends on your hosting environment as much as on DataViews itself.
Written against WordPress 7.0.2, current stable at the time of writing. WordPress 7.1 (scheduled 2026-08-19) refines DataViews further, migrating it onto newer internal design components, without changing the three layouts or the filtering model described above, per the WordPress core team's own roadmap post. Last verified 2026-08-18.
