Import from LucidLink

If your team works out of a LucidLink filespace, Eddie can read footage from it directly — no syncing the files down to your machine first, and the transfer runs server-side so you can close the tab once it starts.

Before you start

LucidLink has no public-link concept: a LucidLink "direct link" only works for someone with filespace access. So Eddie reads your filespace through a service-account token you connect once:

1. Create a service account with access to your filespace in the LucidLink admin portal, and copy its token.
2. On the import screen, click LucidLink, choose Browse LucidLink, and paste the token when asked.

The token is stored encrypted server-side and never leaves Eddie's backend. If your Eddie workspace has LucidLink connected, that shared connection is used — teammates don't each need their own token.

Two ways to import

Browse the filespace. After connecting, pick a filespace (if you have several), browse folders, and multi-select the media files you want. Press Import.

Paste a link or path. The LucidLink dialog also accepts:

• a direct link copied from the LucidLink app — lucid://filespace/path/to/folder
• a filespace path — myspace.domain:/footage/day1
• a bare path like /footage/day1, when you have exactly one filespace connected

A pasted reference can be a single file or a folder — folders are walked, subfolders included, and Eddie lists what it found before you commit. Imports are capped at 1,000 files per import.

What gets skipped

• Non-media files in a folder aren't offered.
• Camera RAW that needs a vendor SDK — REDCODE RAW (.r3d), Blackmagic RAW (.braw) and Canon Cinema RAW Light (.crm) can't be read by a cloud import, so the browser doesn't offer them. Make proxies or optimized media in your NLE and import those, or use the desktop app for RAW workflows. See Working with RAW footage.

Good to know

• Cloud imports are billed on measured footage length. Durations aren't known until the files are processed, so the cost shows as pending at pick time and settles once the footage is measured.
• The desktop app has the same LucidLink integration, if you prefer importing from there.

Troubleshooting

• "LucidLink isn't connected" — pasting a lucid:// link only works once a service-account token is connected. Choose Browse LucidLink and connect first.
• A bare path won't resolve — with more than one filespace connected, Eddie can't guess which one you mean. Use the filespace:/path form.
• Connection fails entirely — disconnect and reconnect LucidLink from the Integrations screen, then try the import again. Still stuck? See Connect cloud storage.
• An import sits in processing for a long time — see Import stuck or failed.