Files and Drive

Files & Drive

Generated assets — and any files you upload — live in Picsart Drive, your centralized cloud library. Outputs from every model land in one place, so you don't download from one tool and re-upload to another.

Save generations to Drive

CLI:

gen-ai generate -m flux-2-pro -p "a poster" --save-to-drive
gen-ai generate -m flux-2-pro -p "a poster" --drive-folder "Campaign Q3"

When saving, the CLI uses an LLM-generated descriptive filename and (for video) an ffmpeg thumbnail — matching the web app's behavior.

MCP: generation tools write to Drive when the Drive option is enabled for the call.

Upload

gen-ai upload ./photo.jpg                  # single file
gen-ai upload ./assets/                    # a whole folder
gen-ai upload ./photo.jpg --name "Hero"

{ "name": "picsart_upload", "arguments": { "filePath": "/path/to/photo.jpg", "name": "Hero" } }

Uploading returns a Drive file you can then feed into a generation as an input image/video.

Browse & organize

gen-ai list --folders          # list Drive folders
gen-ai list                    # list files (JSON-ready)
gen-ai download <uid>          # download a Drive file

{ "name": "picsart_drive_folders", "arguments": {} }
{ "name": "picsart_drive_list",    "arguments": { "folderId": "<id>" } }
{ "name": "picsart_drive_create_folder", "arguments": { "name": "Campaign Q3" } }

Drive commands browse your real root folders — they are not scoped to the AI Playground folder.

Materialize a URL

picsart_materialize_url turns a remote asset URL into a Drive-hosted file, which is useful when a model needs an input that lives behind a short-lived or non-public URL.