Notion's New UI Design Update?! | What's changed, tips, and more (June 2025)

Notion’s June 2025 UI update makes databases look sleeker and more “minimal,” but it also changes how people build, edit, and interact with them—especially in filtered views and when creating properties. The biggest shift lands in the database interface: inline databases now hide view tabs, titles stay pinned at the top, and the default database setup starts out more bare until new pages and properties are added. Full-page databases still support views, but the main area won’t show view tabs unless a new view is explicitly added.

Property management is where the workflow changes feel most immediate. Creating a property now flips the order: users must enter the property name first, then select the property type (for example, choosing “date” after typing “due date”). Editing also gets split from visibility. In settings, the interface separates “editing properties” from “property visibility,” so clicking a property may only allow hiding/showing it; actual edits require going into “edit properties” and selecting the property there. Even calculations move: instead of hovering to calculate columns, the new UI requires clicking into a calculations control to access options like “count all.”

Filtered tables and lists—often used as inboxes—also behave differently. When a filter hides most results, the empty state now includes a “no filter results” style page and removes the older “plus new page” affordance in the same way. That means inbox-style workflows can look emptier or more constrained when there’s nothing matching the filter. Grouping inside filtered views changes too: adding a new page within a group requires clicking a specific control, and the first page in a filtered view comes from a “plus” button rather than from clicking directly underneath the group as before. The creator flags this as an area Notion may need to revisit.

Drag-and-drop is another casualty of the new layout. If someone has been typing tasks and dragging them into a table or list view, that interaction no longer works in the same way. A workaround is to switch the database layout to a gallery view, where drag-and-drop returns.

AI properties are also more hidden and more conditional than before. To add an AI summary, users must first create a compatible base property (typically a text property), then enable “AI autofill” from the property’s AI setup, and only then choose the AI function (like “summary”). Number properties won’t surface AI options, so users may need to convert to a type such as multi-select or text before AI autofill can be configured.

Finally, the update nudges dashboard design. The curved tab layout can make “quick add” buttons look less clean when placed directly above databases, so the creator moves quick-add controls into a separate section or adds spacing via dividers. With fewer visible tabs, dashboards can become more minimal by renaming views with icons and reducing clutter. Database titles, previously often hidden, now make more sense to show when titles sit at the top—particularly for single inline databases. Still, the settings icon change—from the familiar three dots to a slider-style icon—adds friction for tutorials and muscle memory, and several workflow shifts require re-learning.