Upload Failures

File too large

The API accepts images and attachments up to 50 MB per file. A particular uploader or reverse proxy may set a smaller limit; follow the limit shown beside the file picker. DOCX template imports have a separate 20 MB limit.

For screenshots, resize the image to keep text readable without uploading unnecessary pixels.

Upload rejected

Vulnotes checks the file's format as well as its extension. Renaming a file does not convert it. Use an allowed format in the upload dialog; image uploads do not accept SVG.

A 403 response can mean you cannot edit the report or template receiving the file. API integrations also need the write scope for that resource.

Proxy errors or incomplete downloads

An HTTP 413 response usually means the reverse proxy rejected the request body. Ask your administrator to align its upload limit with the application, allowing room for multipart form data. For Nginx, this is controlled by client_max_body_size.

If a downloaded file is incomplete, check the browser's network request, the proxy logs, and available server disk space. A body-size limit rejects an upload; it does not normally truncate a successful upload silently.

Drag and drop not working

Use the file picker to check whether the problem is specific to dragging. If that works, try another browser or temporarily disable extensions that affect the page.