# Developer files | ByteSweep Docs

> Clean build output, package caches, Docker data and WSL disks with ByteSweep, and stop dev servers you forgot about.

Canonical: https://bytesweep.app/docs/clean/developer.html
Last updated: 2026-11-02

## Developer files

Build output, caches and containers add up. These pages are made for that.

Show me on

### On this page

- Turn on developer features
- Clean what builds leave behind
- WSL and Docker disks
- Dev servers

### Turn on developer features

Settings → **General**→**Developer features**. In Basic this adds**For developers** to the sidebar. Advanced always lists these pages.

### Clean what builds leave behind

On Mac

Open **Developer files**.

On Windows and Linux

Open **Developer files**.**Docker disk usage**and**Project build output**have their own sections, and**Select stale projects** picks ones you haven't touched.

On Windows

### WSL and Docker disks

The **WSL and Docker disks**card shrinks their virtual disks. It needs**Run as administrator**.

### Dev servers

On Mac

**Dev Servers**lists what's running. Use**Open Folder**,**Stop…**or**Force Stop…**.**Containers**has**Restart**,**Stop…**and**Open Docker Desktop**.

On Windows and Linux

**Dev Servers**lists**Running projects**and**Docker containers**. Use**Stop project**or**Force stop**.

Docker cleanups on Windows can't be undone. See [what can't be put back](https://bytesweep.app/docs/clean/labels.html#what-cant-be-put-back).

### Ask AI about ByteSweep

It reads these docs, then answers.

Opens in a new tab. Your question goes to them, not to us. AI can make mistakes, so check anything important against these docs.

Updated 2026-11-02. Something wrong here? Write to [support@bytesweep.app](mailto:support@bytesweep.app).