> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/photo-logo-or-video-is-not-displayed.md).

# Photo, logo, or video is not displayed

The blogger card is displayed without an image, the logo does not change, or the video background does not load.

### Symptoms

* blogger card without a photo;
* the logo was not updated after upload;
* the video background does not play;
* the background or logo is visible in the admin panel, but not visible on the storefront;
* images disappeared after content migration.

### Possible causes

* the file was uploaded in an unsupported format;
* the file is too large;
* the link in the database points to a non-existent file;
* the assets were deleted manually;
* the database migration was done without migrating the related files;
* the browser is showing an old version from the cache.

### Allowed formats

| Type             | Formats                                  |
| ---------------- | ---------------------------------------- |
| Logo             | `.png`, `.jpg`, `.jpeg`, `.webp`, `.svg` |
| Card images      | `.png`, `.jpg`, `.jpeg`, `.webp`         |
| Video background | `.mp4`, `.webm`                          |

### What to check

Make sure the file was uploaded through the admin panel, not manually into a random folder.

Check the backend logs:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh logs backend
```

### How to fix it

1. Re-upload the file through the admin panel.
2. Use a supported format.
3. After replacing the background or logo, refresh the page without cache.
4. If content was migrated between languages, make sure not only the database data was migrated, but also the related assets.

{% hint style="info" %}
Media is best uploaded through the admin panel at all times. Then the files are correctly placed into the project structure, backups, and content migration.
{% endhint %}

### When to contact support

If the file uploads without an error but does not appear on the storefront, we need the file URL, the version language, and the latest backend logs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/photo-logo-or-video-is-not-displayed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.