Squish — Local Compression, Built Twice

Squish — Local Compression, Built Twice An architecture diagram generated by Archify. File System Access · showDirectoryPicker() · web/ — no server at all File System Access showDirectoryPicker() Worker Pool · hardwareConcurrency · web/ — no server at all Worker Pool hardwareConcurrency Canvas Pipeline · decode · resize · encode · web/ — no server at all Canvas Pipeline decode · resize · encode Source Folder · on your disk · Architecture component Source Folder on your disk web/ · one page, no backend · Architecture component web/ one page, no backend Support Gate · explains, not breaks · Architecture component Support Gate explains, not breaks Destination Folder · subfolders preserved · Architecture component Destination Folder subfolders preserved desktop/ · Electron · mac + Win · desktop/ — same guarantee, native codecs desktop/ Electron · mac + Win Electron main · no renderer access · desktop/ — same guarantee, native codecs Electron main no renderer access sharp + ffmpeg · native codecs · desktop/ — same guarantee, native codecs sharp + ffmpeg native codecs you pick the folder real folder handle walks the tree one file per worker writes straight back no API → explains the same folders IPC image or video writes to disk web/ — no server at all desktop/ — same guarantee, native codecs Legend Frontend Backend Database Security

No server at all

  • • A normal online compressor makes you upload every file and download the results
  • • showDirectoryPicker() hands the page a real handle to a folder on disk
  • • Compressed files are written straight into the destination, subfolders intact

An explanation, not a broken UI

  • • Safari and Firefox have not shipped the File System Access API
  • • So the app shows a gate that says exactly that
  • • Better than a picker that opens and a save that silently never happens

Built twice on purpose

  • • The browser build runs decode, resize and encode on a pool sized to navigator.hardwareConcurrency
  • • The Electron build uses sharp for images and ffmpeg for video
  • • Either way the files never leave the machine — that is the whole point