Import Failures

Read the dialog explanation and details first. When reporting a problem, include the device, file format, and the details shown to help identify which step failed.

Unsupported Format

The system or browser may not support the file's audio/video codec. Some app import paths try system decoding or conversion. If they still fail, use another tool to convert to MP3, M4A, WAV, or a common MP4 first.

A correct extension can still hide a damaged file. Try another source or check that the system player can play the whole file.

Damaged File or Read Failure

Download or copy the file again and confirm transfer completion. Download cloud media onto the device first rather than keeping an undownloaded placeholder.

Insufficient Space

Free device storage and retry. App Settings manages separation models and playlist render caches; check which kind of data you are deleting. Back up projects separately.

Browsers also have local storage limits. Export important projects first rather than directly clearing site data you still need to free space.

File Too Large or Too Long

File size limits differ from decoding memory budgets. Some prompts ask you to trim first; others directly reject oversized audio. Compression cannot resolve every case. See Large Files and Memory.

Cannot Find a File from a Messaging App

Use “Save to Files” or download it locally in the original app, then select it in GrooveJog. The phone photo library is for videos in Photos; import ordinary audio through the file picker.

Dropping Multiple Files in a Browser Does Not Import

The browser workspace accepts one file at a time. Use the LAN Transfer Webpage for bulk transfers to the app.

LAN Transfer Failure

Check that devices share a network, the app's transfer panel remains open, and the pairing code has not expired. See LAN Transfer for other cases.