Choose CSV or JSON based on the next step
CSV is the practical choice for Google Sheets, Excel, basic dashboards, and teams that need one row per video. JSON is better when your workflow needs nested objects such as channelLinks, channelInfo, or downstream API processing.
Both exports come from the same Apify dataset. Run once, inspect the rows, then download the format that preserves the fields your destination can actually use.
Use the current YouTube actor input fields
For channel collection, add public handles or channel URLs to channel, keep keywords set to false, and use numberOfResults to cap videos per channel. Keep needVideoDetails true when you need complete metadata, engagement signals, channel profile data, publish dates, or transcript attempts.
For faster list-only collection, set needVideoDetails to false. That mode avoids opening every video detail page and is useful when title, URL, thumbnail, channel, duration, relative publish text, and visible views are enough.
Inspect data quality before scaling
Check scrapingStatus on every row and use transcriptStatus instead of assuming that every public video exposes captions. A null transcript can mean that YouTube exposed no caption track, a track could not be fetched, or the detail request failed.
Keep the first run small. Confirm that channelDescription, channelLinksText, publishedAt, viewCount, and any transcript fields needed by your workflow are present before increasing the channel list or scheduling recurring runs.
Export a clean dataset
Open the run's default dataset in Apify and choose CSV for flat spreadsheet work or JSON for nested fields and programmatic processing. Preserve videoUrl or id as the stable record key and keep a run timestamp when comparing repeated exports.
For recurring monitoring, save the tested input as a Task, schedule it, and send completed datasets to a spreadsheet, database, webhook, or API consumer.
Responsible collection
Use public YouTube data for legitimate research, monitoring, and analysis. Review YouTube terms, privacy expectations, and applicable laws, and do not use exported channel data for spam, harassment, or unlawful profiling.