---
title: Disk
description: Upload images, replace the favicon, decide what happens to their camera information, and see how much storage remains.
sidebar:
  order: 9
---

The Disk screen holds files that belong to the selected site. It shows used
storage, the limit your [plan](/dashboard/billing/) sets, and a breakdown by
file type.

## Favicon

The favicon is the small image shown in a browser tab, bookmark, or phone home
screen. Upload a square PNG, JPEG, or WebP for the most predictable crop. A new
favicon is live immediately, with no publish step. Browsers cache favicons, so
an old one may remain visible for a short time.

## Images

Upload PNG, JPEG, or WebP images for use in the site's pages. Each file may be
up to 25 MB. Files are served from the site's own address, not from the
dashboard.

The file list shows each filename, size, upload date, and preview. A coding
agent can also read the stable key a page uses. Deleting a file is
immediate. Check where an image is used before removing it, because a published
page that still names its key can no longer display it.

Hover a picture for two controls: a download that hands back the file you
uploaded, byte for byte, and a delete. The download is there whenever your own
file is still kept, which is what **Camera information** below decides. A
picture that went on the disk before Vizitka kept a second copy has none, and
its tile says so.

The sharing picture for social cards is managed on the [Site](/dashboard/site/)
screen, but it counts toward the same storage limit.

## Camera information

A photograph carries more than the picture: the camera, the lens, the moment,
and from a phone the place. This setting decides what happens to that. It
applies to the next thing you upload, not to pictures already on your disk.

- **Serve a clean copy, keep my own file** is the default and what nearly every
  site wants. Visitors get the picture with the camera's notes taken off it,
  and your own file stays here for you to download.
- **Serve a clean copy, keep nothing else** serves the same clean picture and
  holds no second copy. Nothing here can give that file back to you afterwards,
  so keep your own.
- **Publish my pictures exactly as they are** serves the file as it came off
  your camera. Anyone who opens the page can then read what the picture was
  taken with, when, and, from a phone with location switched on, where you were
  standing. Choose it when publishing capture data is the point.

Your storage counts the file you upload, once, whichever of the three you pick.
The clean copy visitors are served is not counted, so the first option costs you
nothing and the second saves you nothing.