Run the .exe from anywhere and a PORTABLE badge appears in the title bar. Click it to install: for just your account, which needs no admin rights, or for every user on the PC, which asks for permission once and puts KillerShell in Program Files with a Start Menu and Add/Remove Programs entry for everybody.

Installing for all users removes an existing per-user copy, so there is only ever one install and one uninstall entry, and your theme, accent, language and tabs are kept. Settings live in the registry under your own account rather than beside the .exe, so the program stays a single file you can move around.

For fleets, /silent performs the machine-wide install and /uninstall removes it, which is what winget, Chocolatey and RMM tools use. The in-app updater elevates by itself when the installed copy sits somewhere a normal user cannot write to.

Still stuck, or found something broken? The issues page is open to anyone, and a good deal of what KillerShell does started there.

Out of the box KillerShell touches nothing outside its own settings key. If you want Windows to know what it is, the theme flyout has a File associations row that registers it: an "Open with" entry for every text type the editor handles, an "Open in KillerShell" row on folders, drives and the empty space inside a folder, an "Open KillerShell terminal here" row beside it, and the entry that makes KillerShell appear in Settings under Default apps.

Registering and defaulting are two different things, and only one of them is KillerShell's to do. Since Windows 8 the key that records your default app has been protected by a signed hash, so any program claiming to make itself the default is either forging that or about to stop working when Windows notices. KillerShell registers, then opens Settings on its own entry so you can pick per file type. Nothing changes until you do.

.bat, .cmd and .reg deliberately get an "Edit with KillerShell" row rather than taking the open verb. Their double-click runs or merges them, and quietly changing what that means is how someone loses an afternoon. .ps1 is treated as ordinary text, because Windows already opens those in an editor on double-click.

Per-user by default. Tick the box in an elevated window to register for everyone on the PC. Both uninstall paths take it back out again, so a registration never outlives the .exe it points at. If you are running portable the card says so, because the associations will point at wherever that .exe sits right now.

Handing KillerShell a path works whether or not you register anything: KillerShell.exe "C:\logs" browses that folder, and KillerShell.exe "C:\logs\today.log" opens the file in an editor tab.

Download the .exe and run it. There is nothing to install, no account to make and no runtime to fetch. KillerShell opens on your home folder and is ready to work. If you want it in the Start Menu, the PORTABLE badge in the title bar opens the built-in installer.

The window is a title bar, a rail of buttons down the left, a folder tree, one or more tabs, and a status bar. Press F1 at any time for the shortcuts card, which lists every gesture as a plain list or drawn on a keyboard you can hold Ctrl over to see that layer.

Two things are worth knowing up front. Every tab is independent: it can be a folder, a search, a terminal or an open file, and it keeps its own history and results. And Esc is the universal back-out. It closes whatever popup is open, then stops a running search, then offers to quit.

A new tab opens on Home and lists what is there. Double-click a folder to enter it, or a file to open it in whatever Windows uses for that type. The folder tree down the left is rooted at This PC and follows wherever you go. Drag its edge to resize it; the width is remembered.

Navigation follows Explorer exactly. Alt+Left and Alt+Right go back and forward, Backspace also goes back, Alt+Up goes up a folder, and Ctrl+L or Alt+D puts the caret in the address bar so you can type a path. F5 refreshes. The chevron at the end of the address bar lists the folders you have visited recently.

Three views, on the toolbar: list (expandable cards), icons (32 to 256 pixel tiles) and details (sortable columns). Icons run on a virtualizing panel, so a hundred thousand items in tile view stays usable. Two toolbar toggles are remembered between sessions: show hidden and system items (Ctrl+H), and keep folders above files.

In details view, drag any divider to resize the column on its left; the columns to its right keep their widths and slide over. Double-click a divider to put its column back to the width it shipped with. The widths are remembered between sessions. Ctrl+wheel over the list resizes the icons in every view, not just tiles.

Right-click the column headings in details view to pick which columns you want. The same menu is on the Event Viewer grid and the Processes grid, and each one remembers its own choice.

Image files draw a real thumbnail instead of the shared type icon: .jpg, .jpeg, .png, .gif, .bmp, .tif, .tiff and .webp. Each one is decoded once and cached against the file's last-write time, so editing the image refreshes its thumbnail rather than leaving a stale one.

The chevron at the end of the address bar drops down the last fifteen folders you were in, each with its own icon and an X to take it off the list, plus a row that clears the lot. It records folders only, so a search tab or an archive never lands in it.

Ctrl+B opens the bookmarks drawer under the tree. Drop a folder on it to save it, or use the star on the rail for the folder you are in, then jump to the first ten with Alt+1 through Alt+0.

Bookmarks drag to reorder, and right-clicking one opens a terminal there (elevated if you ask for it) or points the Storage Analyzer at it. Files can be dropped onto a bookmark, and onto a folder in the tree, which means exactly what dropping them on that folder in the listing means.

Each tab remembers which rows you had selected, multi-row selections included, and puts them back when you come back to it, with the details strip still showing the same item.

Double-click a .zip, .tar, .tar.gz, .tgz or .gz and you are inside it, browsing with the same rows, sorting, views and keys as anywhere else. The address bar shows the archive and the folder within it, and you can type that path back in to return to it. Alt+Up climbs out of a folder inside the archive and then out of the archive itself, into the folder holding it, so it never dead-ends. Back and forward work the way they do anywhere else.

Nothing was added to KillerShell to read these: zip goes through the framework's own reader and tar is read block by block, so the exe is no bigger for it. .rar, .7z, .bz2, .xz, .cab and .iso are deliberately left alone and still open in whatever you already use for them.

Opening a file inside an archive extracts a copy to a temporary folder and hands it to whatever normally opens that type. It is a copy: edits to it do not travel back into the archive. Entry paths are normalized on the way out, so a crafted archive cannot write outside the folder it is extracted into.

A .zip can be changed from inside KillerShell. Drop files or folders onto it, or paste them in, and they are added where you are; F2 renames an entry and Delete removes one, asking first, because there is no Recycle Bin inside an archive. Anything already in there is never quietly overwritten: the write stops and shows you the clashing names, with Replace or Keep both.

.tar, .tar.gz, .tgz and .gz open read-only on purpose, and a write into one is refused with the reason on the status bar rather than a silent no-op. Adding a single file rewrites the whole archive, so the status bar counts it out as a percentage, and the rebuilt copy is swapped in only once it has been checked - a crash, a full disk or a cancel leaves your archive exactly as it was.

Dragging a file out of an archive copies it out and leaves the entry where it is. A move out would be an extract plus a delete with no way to make them one step, and a failure in between either loses the file or quietly leaves it behind; Explorer treats zip drag-out the same way. Dragging a folder out is not there yet, and neither is New Folder inside an archive.

Two more things do not reach inside: search walks folders on disk, so pressing Search from inside an archive asks you for a folder instead, and the details pane shows a file's name, size and date but its type icon rather than an image preview.

Ctrl+Shift+S opens the search panel on the right edge. The folder you are browsing is already filled in as the scope. Type a term and press Enter. Results stream in as they are found, so you can start reading before the walk finishes, and Esc stops it.

Every term is either a name term, matched against the filename, or a content term, matched against the text inside the file. Click the small mode chip on a term to switch it. Ctrl+Shift+A adds another term, and all of them run in one pass over the tree, each with its own running match count so you can see which ones are hitting.

Terms live in groups. An ANY group matches a file if any of its terms hit; an ALL group needs every term in it to hit. Add a second group when you want something like "any of these three error strings, but only in files whose name contains backup".

Alt+C toggles case-sensitive matching, which is off by default. Ctrl+E puts the caret back in the search box, Ctrl+Shift+L clears the results, and F5 runs the search again.

A name term is a wildcard pattern, the same shorthand Windows itself uses. An asterisk stands for any run of characters and a question mark for exactly one. Plain text with no wildcards in it is treated as "contains", so typing log finds every name with log anywhere in it.

Include and exclude take the same patterns, several at a time separated by semicolons. Include narrows the pass: with *.txt;*.log set, only text and log files are looked at at all. Exclude drops things, and does double duty. A pattern that matches a folder name anywhere in the path, like node_modules, skips that whole subtree, while *.min.js skips those files wherever they sit.

Shift+F7 in the search panel adds a filter row: extension, date modified or size, with is / is not, before / after, over / under. Filters are AND-ed with the terms, so a file has to clear every active filter before any term is tested against it.

Every result is a real file. Click a row to expand it and see the matched lines with their line numbers, Enter to open it, F6 to show it in Explorer, or right-click for everything else. Ctrl+Right and Ctrl+Left expand and collapse every row at once.

The sort button orders by name, location, size or modified date. Ctrl+F filters the visible list live, which is a different thing from searching again: it hides rows you already have rather than walking the disk. Ctrl+Shift+F is the one that walks again, piping this result set into a new tab so the next search only touches the files that survived this one. Chain it as deep as you like.

The copy commands on the right-click menu all act on the whole selection: full path, file name, folder path, matched lines, the files themselves (paste them in Explorer) or a SHA-256. There is also open as administrator, search inside this folder, exclude this folder, properties, and the real Windows shell menu under More Windows options, so anything your other tools add to Explorer is still one click away.

Ctrl+Alt+E exports a self-contained HTML report with its own theme switcher and sortable columns, and Ctrl+Alt+Shift+E exports CSV. Both open anywhere with no dependencies, which makes them easy to attach to a ticket.

Search results and folder listings behave the same way. Ctrl+X, Ctrl+C and Ctrl+V cut, copy and paste files, F2 renames, Delete sends to the Recycle Bin, Shift+Delete destroys (and asks first), and Ctrl+Shift+N makes a folder.

Copy and move run off the interface thread with a progress card showing the current file and a real byte count. If something already exists at the destination it stops and asks, showing both files' size and date, with Replace, Skip or Keep both and a checkbox to do the same for the rest of the batch. Nothing is copied while that question is on screen.

A move within one drive is a rename, so it is instant at any size. Across drives it copies first and only deletes once the copy has landed. Recycling goes through the shell, which is also what puts the operation on Explorer's undo stack, so Ctrl+Z there brings the files back.

Drag and drop works both ways. Drag out of KillerShell into Explorer or a mail client, holding Shift to move instead of copy. Drop onto a browsed folder and Explorer's rules apply: Shift moves, Ctrl copies, and neither means move within a drive and copy across drives. Drop onto a search tab instead and it sets the scope or pipes the files, since there is no folder to drop into.

Ctrl+T opens a tab, Ctrl+W closes one, Ctrl+Tab cycles (add Shift to go backwards), and Ctrl+1 to Ctrl+9 jump straight to one, with 9 meaning the last. Drag tabs to reorder them. On quit you are asked whether to remember the open tabs, and that answer can be remembered too.

F10 gives you a second pane. Right-click the rail button to flip between side by side and stacked. Each pane has its own tabs, its own toolbar and its own folder, so you can drag files from one to the other, or keep a search on the left and a shell on the right.

The two panes share nothing they should not. View mode, icon zoom, row density, the details-view column widths and which columns are showing, and the details strip's open state and height are all per pane, and each pane remembers its own across restarts. On a floating window F10 grows the window and leaves the first pane exactly as it was; on a maximized or snapped window there is nowhere to grow, so the panes split the room they already have.

Each kind of tab gets its own toolbar, because the buttons that make sense over a folder listing do not make sense over a document. A folder tab keeps the location row with back, forward, up, the star and the sort and view buttons. A shell tab swaps it for the live working directory plus new shell, elevate, open folder here, clear and fonts. A document tab gets save, undo, redo, find, go to line, wrap, a settings gear, and readouts for the path, encoding and line ending. Ctrl+F10 hides the pane menubar entirely on whichever pane you are in.

Tabs divide the bar between them, but only down to a point: once they would get too narrow to read, the strip keeps as many as fit and a chevron at the right end lists every open tab so you can jump to one. The tab you are on is always in the strip.

Ctrl+N opens a whole second window if you would rather have two.

Drag a tab off the strip and it becomes its own window, or drop it on another KillerShell window to move it there, with a caret showing where it will land. Every window is its own process, so the tab is rebuilt on the other side rather than moved live, and it comes back as what it was: a folder, a shell in the same directory, an open document, or any of the tool tabs. A document with unsaved changes refuses the drag and says to save it first, rather than dropping the edit on the floor.

Alt+P shows or hides a bottom-anchored file details pane for the item you have selected: type, size, dates, attributes, the full path, and a thumbnail for images or the type icon for everything else. It tracks the selection live and collapses to a thin line when there is nothing to show. Drag its top edge to make it taller. Each pane has its own strip, and each remembers whether it was open and how tall you made it.

F8 opens PowerShell in the folder you are looking at, Shift+F8 opens CMD, and Ctrl+F8 opens PowerShell elevated. The terminal button on the rail does the same on a left click, and right-clicking it lets you pick the host. A shell opened from a result's right-click menu starts in that file's folder.

Ctrl+Shift+F8 is the fourth of the set: CMD, elevated. Ctrl+backtick and Ctrl+Alt+backtick are aliases for the two PowerShell ones, because VS Code and Windows Terminal both train that chord. PowerShell means pwsh where PowerShell 7 is installed and Windows PowerShell where it is not, decided when the tab opens rather than when the app starts, so installing 7 mid-session is picked up on the next shell.

The working directory is tracked live and shown on the shell's toolbar. Click it to edit it in place - type a folder and press Enter to cd the running shell straight there, or press Escape to cancel without changing anything. The right-click menu has copy, paste, select all, clear, a new terminal, open folder here, fonts, and edit or reset the prompt.

KillerShell ships a prompt script you can edit or put back. Your own PowerShell $PROFILE is reachable from the rail menu, the shell's right-click menu or Ctrl+comma. The submenu lists the PowerShell hosts actually installed on the machine, because PowerShell 7 and Windows PowerShell do not share a profile and editing the wrong one is most of the "why is my profile not loading" in the world. It asks each host where its profile is rather than assuming a path, which matters on any machine where OneDrive has redirected Documents. A profile that does not exist yet is created.

The prompt draws powerline separators, a git branch mark and its own chevron, none of which any monospaced font Windows ships actually has. Rather than making you install a Nerd Font, KillerShell carries a 26-glyph, 2.9 KB fallback face and uses it only for the characters your chosen font is missing. Pick any font you like; the prompt still renders.

Ctrl+Shift+C copies the selection, Ctrl+Shift+V pastes, Ctrl+Shift+A selects everything, and Shift+Insert and a plain Ctrl+V paste too. Ctrl+C copies when something is selected and otherwise goes through as the interrupt, which is what it means in a shell. Middle-click pastes.

Right-click opens the menu rather than pasting, on purpose: a stray right-click that dumps a clipboard full of commands into a live admin shell is a bad afternoon. Ctrl+Shift with the arrows or Page Up and Page Down scrolls the view without disturbing the line you are typing, and Ctrl+plus, Ctrl+minus and Ctrl+0 change and reset the font size.

F7 on a result, or the Edit row on its right-click menu, opens that file in a tab. You get syntax highlighting, line numbers, undo and redo, find with Ctrl+F, go to line with Ctrl+G, save with Ctrl+S, and a full right-click menu. Word wrap is on by default.

F7 with nothing selected opens an untitled document instead, the same one the pencil on the rail gives you. Find has match case, whole word and regular expression options behind its own chevron; it finds rather than replaces. Save As uses KillerShell's own file dialog, not the Windows one.

Highlighting covers the formats a field tech actually opens: .bat and .cmd, .reg, .ini and its relatives, .yml, .log and .csv, on top of the programming languages the editor already knows. The registry one colors a key deletion and a value deletion in the danger color, because both are one character away from the line that merely sets something. The log one lights severity words, timestamps, GUIDs, error codes and paths, and deliberately leaves everything else as body text.

Your encoding is preserved, never invented. A byte-order mark that was there stays there, a file without one stays without one, and bytes that are not valid UTF-8 fall back to the system codepage rather than being replaced with question marks. The bar under the document shows the encoding and the line ending, because whether PowerShell 5.1 will read your script depends on both and neither is visible in the text.

The encoding readout is also a picker: click it to choose what the next save writes - UTF-8, UTF-8 with BOM, UTF-16 LE, UTF-16 BE or ANSI. Nothing is rewritten until you save.

The gear holds the settings that describe how you read code rather than what one file is, so they apply to every open document at once: line numbers, highlight the current line, show spaces and tabs, insert spaces instead of tabs, and indent width. The editor has its own slot in the Fonts dialog, filtered to fixed-width faces, and Ctrl+wheel over the text changes the same size.

Closing a tab with unsaved changes asks before it discards anything, and a document with unsaved changes shows a dot in front of its tab title. Anything over 32 MB is refused rather than opened slowly: the editor holds a document in memory and builds its indexes over the whole of it, so a file that size would not open slowly, it would lock the window.

Click the document's path on the editor toolbar to edit it in place - type a new path and press Enter to rename or relocate the file the tab points at. If a save fails because the file needs administrator rights, Ctrl+F7 opens a new document with an admin-save retry, so a permission error does not cost you the text you just wrote.

F9 opens the Processes/Services tab, a singleton the same way the rail's task-manager icon is - opening it twice just switches to the one already open. Ctrl+F9 opens it elevated. Ctrl+period switches between the Processes and Services views, and the tab's own title follows: it reads Processes or Services depending on which one is showing, so a glance at the strip tells you which grid you left it on.

Processes is a live grid of everything running, with real CPU percentages and the command line, path and owner filled in from one bulk query rather than one call per row. Services is the same grid pointed at Windows services, with startup type, path and account. The filter box matches the path and the user or account too, not just the name, and the column headings right-click to show and hide columns. Double-click a row for a details card with Previous and Next paging through the grid.

With a row selected and the grid focused: Delete ends the process (or stops the service), Ctrl+R restarts a process, Ctrl+O opens its file location, Ctrl+Shift+A restarts a process as administrator, and Ctrl+S starts a stopped service. Every one of those asks first, in KillerShell's own dialog rather than a Windows message box.

F11 opens the Performance tab, another singleton. It is a scrolling two-column grid of full-size cells rather than a list of thumbnails beside one big graph, so every metric is live at once and nothing has to be selected to be readable: CPU, RAM, then one cell per physical disk, one per network adapter and one per GPU, all enumerated from the machine rather than assumed to be one of each. There is no elevated variant and none is needed - every counter it reads is available to an ordinary user account.

Each cell has a header carrying its name, a one-line live summary and the hardware it is reading, a full-width graph or two, and its numeric fields underneath. The button on the right of a header makes that cell full width or half width again, and dragging a header moves the cell: the cells shuffle live as you drag, so the reorder is its own preview. The arrangement is remembered, and new hardware appears without disturbing what you have already laid out.

Click the CPU graph and press L to toggle between one overall trace and a grid of per-logical-processor traces, so you can see whether load is spread across cores or pinned to one. The same toggle is on that graph's right-click menu as Show logical processors, if it is easier to find than to remember.

F4 opens the Storage Analyzer tab and Ctrl+F4 opens it elevated, which is what you want on a system drive, since an ordinary account gets Access Denied on a good deal of it. The hard-drive icon on the rail does the same on a left click, and right-clicking it offers both. Put a folder or a drive in the target box, or pick one with Browse, and press Scan. The walk runs one worker per logical processor and never follows a junction or a symlink, so nothing is counted twice, and the status bar shows directories, files, bytes and skipped folders as it goes.

What you get is a treemap of the WizTree and WinDirStat kind: one rectangle per file, its area proportional to its size, with folders drawn as nested outlines around their contents. Double-click a folder to zoom into it, and use the breadcrumb above the map to climb back out. Right of Scan, Depth drops down All, 1, 2, 3 and 4 to limit how many folder levels get their own rectangles; at 1 each top-level folder is a single solid block, which is the quickest way to see where the space went. Min size drops down All, 1 MB, 10 MB and 100 MB. Both are view filters applied while drawing rather than rescans, so they are instant, and neither loses a byte: a capped folder is drawn as one rectangle carrying its whole subtree, and a hidden small file still counts inside the folder holding it. Either one carries a small badge showing its value while it is set to anything other than All. The last pair of buttons colors the map by file type or by top-level folder. Depth, minimum size and coloring are all remembered between sessions.

With the tab focused, Ctrl+Enter starts the scan, D cycles depth, M cycles the minimum size, C switches coloring, Enter zooms into the selected folder, Backspace zooms out a level, Home goes back to the scan root, Delete sends the selected item to the Recycle Bin, F5 rescans and Esc stops a running scan. The single letters are single letters on purpose, so they only apply while the caret is not in the target box - typing a path there types a path.

Right-click a rectangle to open it in a new tab, show it in Explorer, copy its path or delete it; the same menu carries the two coloring choices and Rescan, and those are there on empty space too. Delete is the only destructive thing in the tab and it always goes to the Recycle Bin through the shell's own confirmation, so nothing here can destroy a file; the map updates in place afterwards with no rescan. The footer shows the hovered or selected item's full path, its size and its share of what is on screen, alongside the drive's total and free space. There is also an Analyze storage row on the file listing's right-click menu and on a bookmark's, which points the tab at that folder and starts scanning straight away.

Ctrl+F12 opens the Event Viewer tab. There is no unelevated way in - it always opens elevated, because the Security log it reads refuses to open for a process that is not already administrator.

Pick a log - Application, System, Security, or all of them at once - and a level, All, Error, Warning or Information. The filter box narrows what is already loaded by source, message, category or event ID without going back to the log, and the grid sorts newest first with a colored severity dot per row. It reads up to two thousand records per log and streams them in rather than making you wait for the lot. Right-click a row to copy its message, or to copy the full details as a block you can paste straight into a ticket.

Double-click a row for the details card: every field the event carries, the raw XML with syntax highlighting behind Alt+X, a one-click web search for the event ID on Alt+S, and the arrow keys to page through the grid without closing it. This tab has no keys of its own beyond that card - everything that works on it is the window's.

Ctrl+F11 opens the Registry Editor tab, also always elevated, for the same reason as Event Viewer - there is no unelevated way in.

All five hives are there, loaded lazily: a key's children are read when you expand it, never walked ahead of time. Values are formatted for their type - DWORD and QWORD in hex and decimal, binary as hex byte pairs, multi-string entries visibly separated - and a pathologically large value is capped in the grid with a note saying how much was cut, while Modify still reads and writes the whole of it. The path readout above the tree is editable: type a key path and press Enter to go there.

The right-click menus carry New (a key, or any of the six value types), Rename, Delete, and copy the name or the full path. Every value edit goes through one dialog that adapts its input to the value's type and needs an explicit Save - nothing here commits because focus moved. Deleting a key says out loud that it takes every subkey and value nested underneath it, in KillerShell's own confirm dialog rather than a stock message box.

With the tree or grid focused: F2 renames a key or value, Delete removes one, Ctrl+F finds a key or value name, Ctrl+C copies the full path, Enter opens Modify on a value, and F5 reloads the selected key from disk. Find searches the part of the tree that is loaded, which is what keeps it instant instead of walking the whole registry, and says so when it comes up empty.

Each tool has its own icon on the rail, and that icon lights in the accent while a tab of that kind is open anywhere in the window - Processes, Performance, Storage Analyzer, Registry Editor and Event Viewer. Background tabs and the second pane count, so only closing the last one of a kind puts the icon out. Each of these tabs is a singleton: pressing its key again brings you back to the one you already have rather than opening a second.

Shortcuts work anywhere in the window; open dropdowns, the date box and the results filter keep Enter for themselves. This is the full reference, grouped exactly as the in-app card groups it.

The window is eight applets sharing one frame, so a key needs two answers, not one: what kind of thing it does, and where it does it. The colored headings are the first - search, navigation, tabs, view, file, editing, help. The plain headings above them are the second: Everywhere is what the window itself runs whatever tab is showing, and the rest belong to one tab each.

That is what lets a key mean two things honestly. Ctrl+Shift+C is Copy full path in the listing and Copy in a terminal. Ctrl+Shift+A adds a search term, restarts a process as administrator, or selects all in a terminal, depending on where you are. Neither was renamed to avoid the clash; they are simply different scopes.

The Event Viewer has no keys of its own, so it has no section here - everything that works on it is in Everywhere, and so is the Performance tab.

Thirteen themes: Dark, Light, Black, 98SE, Blood, Greed, Cyanotic, Ectoplasm, Decay, Malaise, Sepulchre, Delirium and Mourning. Dark, Light, Black and 98SE each carry six accent colors; the other nine are a palette on their own. The paint roller at the bottom of the rail switches them live, and nothing restarts.

The flyout stays open while you try them, and the switch is a crossfade rather than the window changing in pieces. Two more rows live under the themes: the Fonts dialog, and the File associations card.

The Fonts dialog has three slots: the app, the terminal and the editor. The terminal and editor lists are filtered to fixed-width faces. Roll the wheel over a list to browse faces and each one applies as you land on it, so you see it before you commit to it.

Roll the wheel over the wordmark in the title bar to resize the whole app, about 2% a notch between 70% and 250%. It reflows rather than stretching a bitmap, so text stays sharp, and the setting is remembered. The density button on the rail separately controls how tightly the result rows are packed.

The language menu is the globe on the rail, above the theme button. Eleven languages, switched live: English, Spanish, German, French, Turkish, Polish, Czech, Japanese, Chinese in both Traditional and Simplified, and Bengali.

KillerShell draws its own icons rather than borrowing the Windows shell ones. Folders have their own art, and the ones that mean something get drawn as themselves rather than as a generic folder: Home, Desktop, Documents, Downloads, Pictures, Music, Videos, Favorites, Program Files and Windows, plus drives and This PC. Every kind of tab has one too - shell, admin shell, a shell that has exited, document, Processes, Event Viewer, Performance and Registry Editor - and the tree, the bookmarks, the listing, the tab strip, the overflow list and the recents menu all resolve through the same place, so nothing ends up with a different icon from its neighbor.

The 98SE theme swaps the whole set live for period art rather than leaving the brand icons sitting on it. That art is Chicago95, upscaled with nearest-neighbor so the pixels stay pixels, and every icon is credited to its source in the repo.