Redesign the current custom Windows file explorer so it can serve as a realistic replacement for native Windows Explorer.
The redesign must preserve the strongest parts of the current concept while making it feel:
- native to Windows
- fast and low-overhead
- fully usable in both light mode and dark mode
- modern, but restrained
- more responsive and less visually heavy than the Files app
This document is both a design brief and a long-term reference for future UI work.
This app is not supposed to be a flashy alternative file manager. It is supposed to feel like:
“the file manager Windows should have shipped: native-feeling, theme-aware, compact, fast, and visually quiet.”
The design should sit between:
- Windows Explorer for familiarity, predictability, and shell-like behavior
- Files for visual polish, modern structure, and overall cleanliness
But it must avoid the biggest weakness of Files:
- feeling heavy
- feeling layered
- feeling more like a styled desktop app than a shell component
- being slow
Take the structural familiarity of Explorer, the clarity and polish of Files, strip away most of the decorative weight, and design a UI that feels engineered for speed.
- The app must support light mode and dark mode as first-class experiences.
- It must match the Windows system theme automatically by default.
- It should allow a manual theme override in settings.
- It should feel appropriate as a daily driver replacement for Explorer.
- It should visually communicate speed, reliability, and low overhead.
- The redesign must not assume a web-app aesthetic.
- The design must stay compact, dense, and efficient, without becoming cramped.
Users should immediately understand the app if they know Windows Explorer.
Preserve familiar patterns:
- sidebar-based navigation
- breadcrumb/path bar
- file list behavior
- keyboard shortcuts
- context menu expectations
- selection model
- drag and drop behavior
- rename behavior
- sorting and column logic
Every visual decision should support the impression that the app is lightweight and immediate.
Avoid anything that makes the UI feel bloated or sluggish.
The app should look current, clean, and intentional without becoming glossy, oversized, or overly “app-like.”
The UI should show a lot of information without looking cluttered.
Light mode and dark mode must both feel intentionally designed. Neither should feel like a quick inversion of the other.
The application should use a classic, Explorer-like structure because that remains the most effective mental model for file navigation.
Use a three-part structure:
- Left sidebar for global navigation
- Top header area for movement, actions, and path/search
- Main content pane for current directory contents
Optional panes like preview/details should exist only if enabled and should not complicate the default layout.
The sidebar is for global navigation context, not for heavy visual experimentation.
It should contain:
- Home
- Favorites / Quick Access
- Drives
- Optional cloud storage entries
- Optional sections like tags, network, libraries, etc.
The sidebar should feel:
- compact
- structured
- clearly navigational
- lighter than Files in visual weight
- closer to shell UI than app navigation UI
- Keep it fixed-width and relatively slim
- Use muted section headers
- Use compact rows
- Use clear active and hover states
- Prefer collapsible groups over visual clutter
- Do not over-style with cards, oversized surfaces, or excessive nesting
- Avoid making it look like a website side menu
- Active item should be obvious but not loud
- Section labels should be secondary
- Icons should support fast scanning
- Spacing should feel efficient, not airy
The header should support navigation and actions without becoming visually heavy.
The recommended structure is two rows:
Include:
- Back
- Forward
- Up
- Refresh
- New tab, if tabs exist
- Contextual file/folder actions if appropriate
- Status indicators aligned to the right
Include:
- Breadcrumb path bar
- Search field
This is preferred over forcing everything into a single crowded strip.
The top area should feel:
- crisp
- compact
- immediate
- shell-like
- more disciplined than Files
- Use small, efficient controls
- Avoid oversized buttons or excessive pill styling
- Use disabled states clearly
- Keep visual noise low
- Avoid decorative chrome
The path bar is one of the most important controls and should support both mouse-driven and keyboard-driven workflows.
- Clickable breadcrumb segments
- Editable path input mode
- Clear current-location emphasis
- Fast transitions between display and edit states
The path bar should feel:
- precise
- familiar
- native to Windows expectations
- more refined than raw text, but not ornamental
This area should be treated as a functional control, not a decorative element.
Search should exist because it is useful, not because Explorer has one.
- Placed in the header area, typically alongside the breadcrumb row
- Compact by default
- Visually integrated
- Easy to ignore when not needed
- Should not dominate the layout
Search should feel like part of the shell, not like a web app’s global command box.
This is the core working area and should be the visual center of the entire app.
The main pane should dominate the composition more than the sidebar or header.
This area must feel:
- instant
- stable
- crisp
- highly scannable
- low overhead
This is the most important view for the app. If this feels wrong, the whole product feels wrong.
Use a clean list/table view as the main default.
Suggested columns:
- Name
- Type
- Modified
- Size
- Name should be the widest column
- Size should be right-aligned
- Metadata should be visually de-emphasized
- Column resizing should be supported
- Sorting should be obvious and efficient
- Compact but readable row height
- Clear hover state
- Strong selected state
- Minimal visual noise
- No unnecessary striping by default
- Sticky header only if it feels native and useful
- Simple and fast-loading
- Easy distinction between folders and files
- Symlinks should have a clearer indicator than text alone
- Avoid excessive icon detail if it harms performance or scan speed
- Filenames should be visually strongest
- Type / date / size should be secondary
- Selection must be very clear
- Hover must provide click affordance without becoming distracting
The list should feel more like a native data view than a styled web table.
Tabs are acceptable only if they remain cheap and utility-focused.
- small in visual footprint
- quick to open and switch
- low memory overhead in feeling and behavior
- more like shell tabs than browser tabs
- oversized browser-style tab chrome
- heavy animations
- bloated tab bars
- features that make tabs feel expensive
If tabs feel heavy, they undermine the entire design goal.
The app should automatically match the Windows system theme.
- manual override: Light
- manual override: Dark
- optional “Use system accent color” behavior if appropriate
Do not design dark mode first and simply invert it for light mode.
Both themes must preserve the same hierarchy, spacing logic, and product identity.
Dark mode should feel:
- calm
- precise
- low-glare
- engineered
- contrasty enough for long sessions
- neon accents
- overly blue surfaces everywhere
- excessive glow
- overly soft low-contrast text
- heavy glass or acrylic effects
Dark mode should look modern without becoming flashy.
Light mode should feel:
- crisp
- clean
- native to Windows
- structured without looking sterile
- pure white everywhere
- flat, borderless emptiness
- weak surface hierarchy
Use subtle separation between:
- window background
- sidebar
- toolbar/header
- content pane
Light mode should feel like a first-class shell theme, not a fallback.
The app should use layered surfaces, not just a single background color with text on top.
Use clear but restrained distinctions between:
- app background
- sidebar surface
- header/toolbar surface
- content surface
- selected state surface
The hierarchy should stay stable across both themes. Only the palette should shift, not the structure or interaction model.
Typography should be:
- clean
- system-friendly
- compact
- highly legible
- Use a modern sans-serif that feels at home on Windows
- Keep primary labels clear and readable
- De-emphasize metadata with weight/color rather than shrinking too aggressively
- Do not make the UI tiny just because it is a power-user app
- Primary: filenames, current path, selected content
- Secondary: column headers, control labels, section titles
- Tertiary: metadata, status indicators, minor labels
Use color sparingly and purposefully.
- Accent color for selected states, active navigation, and small emphasis points
- Folder/file distinction should be fast and obvious
- Metadata should remain more muted than filenames
- Do not rely on color alone for meaning
- too many accent tones
- loud gradients in the working UI
- decorative color use that competes with content
The actual working interface should be visually quiet.
The redesign must preserve or improve key shell interactions.
- fast hover response
- crisp selection feedback
- intuitive multiselect behavior
- predictable right-click behavior
- inline rename that feels clean and stable
- drag-and-drop affordances
- obvious keyboard focus states
The interface should feel familiar enough that users do not need to relearn file management.
This is critical. The slowness of Files is a primary reason this redesign exists.
Therefore, the design must avoid visual patterns that commonly make desktop apps feel sluggish.
- too many nested surfaces
- excessive translucency
- expensive blur effects
- oversized shadows
- heavy animation
- complex decorative transitions
- overbuilt icon systems
- browser-like chrome if not necessary
- large padded layouts that waste space and scrolling efficiency
- subtle effects only
- flat or lightly layered surfaces
- simple transitions
- compact interaction zones
- strong alignment and hierarchy instead of decoration
The UI should look like it was designed by people who care about frame time.
Files is an inspiration, not the blueprint.
- modern cleanliness
- good overall structure
- polished proportions
- clear organization
- friendly visual tone
- visual heaviness
- extra decorative layering
- too much softness/floatiness
- overbuilt top-level chrome
- anything that makes it feel slow or “styled first, shell second”
Do not make “a prettier Files.” Make “a faster, more native-feeling Explorer replacement that learned the right lessons from Files.”
Explorer should remain the baseline for behavioral familiarity.
- discoverability
- shell mental model
- navigation familiarity
- low cognitive load
- standard file-management behavior
- cleaner hierarchy
- modern surface treatment
- more consistent theme behavior
- stronger dark mode
- better polish
- more intentional spacing and typography
The final interface should feel:
- native
- capable
- compact
- deliberate
- modern
- calm
- engineered
- fast
It should not feel:
- flashy
- playful
- trendy for its own sake
- oversized
- browser-like
- over-animated
- consumer-app glossy
Design a modernized Windows Explorer replacement that automatically follows the system light/dark theme, feels compact and shell-native, and uses Files only as a source of visual polish rather than as a structural or stylistic blueprint. Keep the familiar Explorer mental model, use a flat but refined sidebar, a crisp two-row top area, and a highly optimized main file list built for scan speed. Every design choice should reinforce the impression that the app is lighter, faster, and more dependable than Files.
Use this document as the design authority for the redesign.
Redesign the current file explorer UI and output a refined design proposal that includes:
- overall layout direction
- component-by-component redesign notes
- light mode guidelines
- dark mode guidelines
- hierarchy and spacing rules
- interaction rules
- performance-aware visual constraints
- a concise design system section
- any recommended simplifications versus the current design
- Do not redesign it into a generic web app
- Do not make it look like a prettier clone of Files
- Do not sacrifice density or usability for style
- Do not overuse acrylic, blur, glow, or oversized spacing
- Keep it believable as a native daily-use Explorer replacement
- Assume speed and responsiveness are core product values
The output should be specific enough that it can guide implementation and future design decisions, not just offer vague aesthetic advice.
Design it like the file manager Windows should have had: native-feeling, theme-aware, compact, calm, modern, and visibly faster than Files.