Skip to main content
Melfarkan
Known Participant
April 25, 2026
Question

Kling 3.0 Paid Version Not Working

  • April 25, 2026
  • 1 reply
  • 39 views

I have been trying to generate videos using Kling 3.0. I currently have a premium plan, but ironically I cannot use it because the system does not even consume credits.

In just one day of use, these have been the most recurrent issues:

  1. Images cannot be uploaded.
  2. Files cannot be downloaded to my computer. This is not a device issue—I am using a Mac and I am an experienced user.
  3. Paid video assets cannot be uploaded into Kling 3.0.
  4. Video generation fails because the system flags content as “violating user guidelines,” even though I am only using prompts with fully clothed adult characters and neutral scenarios.

Frankly, I did not expect this level of malfunction from a paid service.

I would appreciate a clear explanation and a prompt resolution.

    1 reply

    droopydog500
    Community Manager
    Community Manager
    April 27, 2026

    Hi ​@Melfarkan,

         Images cannot be uploaded.

    Are you dragging the image in or clicking it to get a dialogue box? Are you getting an error or is it silently failing? What is the file type of the image you are using? What browser are you using? 


        Files cannot be downloaded to my computer. This is not a device issue—I am using a Mac and I am an experienced user.

    Are you getting an error or is the download silently failing?  If you go to you generations page (on the main Firefly page, select “Your Stuff” on the left and then “generation History”, can you download from there? 


        Paid video assets cannot be uploaded into Kling 3.0.

    What happens when you try? Can you upload other assets?

     

        Video generation fails because the system flags content as “violating user guidelines,” even though I am only using prompts with fully clothed adult characters and neutral scenarios.

    Can you please include the image you used and the full prompt? The amount of skin visible is not the only thing that can trigger this error.

     

        droopy

     

     

    Adobe Community Expert (not an Adobe employee)