> ## Documentation Index
> Fetch the complete documentation index at: https://cal.com/help/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting events

> Fixes for the cover image upload, and a plain list of what the Events feature does not do yet.

## The cover image will not upload

If you see **Unable to import the image, please try again** or **Could not upload image**, work through these in order.

<Steps>
  <Step title="Save the event">
    Select or drag in the image, then scroll down and select **Save** (or **Update**) in the editor. The upload only takes effect once the event is saved, and this button is easy to miss. This resolves most reports.
  </Step>

  <Step title="Check the file and try another route">
    Confirm the file is under 10 MB and in a standard format such as PNG or JPG. Try **Browse** instead of drag and drop, or try a different browser. Some people hit this on Microsoft Edge specifically.
  </Step>

  <Step title="Contact support">
    If the upload still fails with a valid file after saving, this is a known issue our engineering team is working on. Contact support with the exact error message, the file format and size, your browser and operating system, and a screenshot or short screen recording.
  </Step>
</Steps>

## What events do not support yet

| Not supported                           | Detail                                                                                                                                                                   |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Recurring events                        | Events are one-time by design. There are no multiple dates and no slot picking. Use a [recurring Link](/help/event-types/create-recurring) if you need something that repeats |
| A management API                        | Events are managed through the web app only. The Platform API's event-type endpoints do not cover events                                                                 |
| Stripe or PayPal                        | Paid events run through Cal Pay only                                                                                                                                     |
| Paid events with approval or a waitlist | Turn both off before charging for an event                                                                                                                               |
| No-show or attendance tracking          | The roster records the guest's RSVP response, not who actually attended                                                                                                  |
| Changing the URL after publishing       | The slug is fixed once the event goes live. It can only be changed while the event is a draft                                                                            |

AI cover images and **Translate using AI** exist in the editor but are gated by plan or organization, and may show an upgrade prompt where they are not enabled.

If you need something on this list, let our support team know. Feature requests are shared with the product team.

## When to contact support

Get in touch if you hit an error that persists after the steps above, for example:

* An event that will not publish after form errors are fixed and changes are saved
* A payment section that stays greyed out after Cal Pay is set up correctly
* A registration or RSVP that fails
* A map or calendar sync that keeps failing
* A refund that failed and cannot be completed from your side

## Related

* [Create and publish an event](/help/events/create-an-event)
* [Paid events with Cal Pay](/help/events/paid-events)
* [What is a Cal Event](/help/events/what-is-a-cal-event)