Screenshots and images without the hassle
Images are dropped or pasted where they are needed, kept in one media library, and served resized to the width the page needs, with long browser caching.
The problem
Adding a screenshot to a case study used to mean: upload it somewhere, copy an address, paste it into a field, and hope nobody resizes the browser. The result was full-size images on every page and broken links when a file was replaced.
How dok.sh solves it
- Drop or paste where you work: on an image field, into a gallery or straight into a Markdown text. The image is uploaded and inserted in place.
- One media library for every upload, with search, filters by type, the size of each file and a picker that any editor can open.
- Resized on request: pages ask for
/files/<id>?w=640and get an image at that width. Only a fixed list of widths is allowed and resized images are kept in a bounded cache, so nobody can make the server resize to arbitrary sizes. - Cached for 30 days with an ETag: a file never changes under the same id, so browsers can keep it.

The result
Adding a screenshot takes one paste, and visitors download images sized for their screen.
Technologies
Spring Boot, GridFS, Image resizing, Caching
- Published: 2026-11-03
- Project: dok.sh — Portfolio and CV Platform
- Case study