Instagram Reels audio_name: you can rename the audio only once

Meta lets you rename a Reel's original audio once, in the container or on the audio page. Decide the name before publish and detach the track with Sume.

5 min readSume
All posts

audio_name is a Reels-only container parameter that sets the name of your Reel's audio, and Meta says you can rename it only once, either while creating the Reel or later from the audio page. So the safe move is to decide the name before the first publish and send it in the container, because a typo you fix later spends the only rename.

This comes from Meta's IG User Media reference, read 2026-10-02. Sume does not set Instagram audio names, but audio detach can give you the track as a file so the name you choose matches something you can name and keep.

What does audio_name do, and what is the catch?

Meta lists audio_name as "For Reels only": the name of the audio of your Reels media. The catch is the single rename: either at creation or afterwards from the audio page, not both, and not repeatedly.

On the same page, a separate limitation says music tagging is only available for original audio. That is why the audio you upload matters, and why a name worth keeping is a name you checked.

audio_name facts, Meta reference read 2026-10-02
QuestionAnswer from Meta
Which media types?Reels only
How many renames?Once
Where can the rename happen?While creating the reel, or from the audio page
Related limitMusic tagging only for original audio

How do I pick a name I will not regret?

Treat the name as a field in your publishing record, not a caption afterthought. Write it down next to the video URL and the caption, and review it with the same eyes as a title.

A few rules keep it clean: name the sound after what it is, not the trend; keep one spelling for a series so reused audio looks like one family; and never put a brand or person in the name unless that account is the origin of the sound.

Review the name the way you would review a headline: read it aloud, check the spelling, and confirm it still makes sense when the Reel is shown out of context in the audio page.

  • Draft the name when you approve the cut, not at publish time.
  • Keep it short enough to read in the audio row of a phone.
  • Store it with the job id so a re-publish sends the same string.
  • If a collaborator owns the audio, ask them for the name before you spend the rename.

Where does Sume fit?

If the Reel's sound is a voiceover or music bed that you want to reuse across several Reels, extract it once. Audio detach turns a Sume-hosted clip's track into a durable wav or mp3, and timeline audio can join slices into a reusable merged file. Reusing one file keeps every Reel's sound identical, so one name fits all.

Sume has no endpoint that publishes to Instagram or renames audio on the platform; that stays in your Graph API call. Poll the detach job through the normal jobs and results flow.

What does the container look like?

Add audio_name next to the other Reels fields. The reference lists it with collaborators, cover_url, user_tags, location_id and thumb_offset. Original audio and the 2026 audio API are covered in media_audio_type; read that if your Reel uses library music.

curl -X POST "https://graph.instagram.com/v26.0/$IG_USER_ID/media" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -d "media_type=REELS" \
  -d "video_url=https://media.sume.com/artifacts/artf_demo/reel.mp4" \
  -d "audio_name=Studio walkthrough, original sound"

What if the audio is already published?

If the same audio was already used by an earlier Reel, you cannot assume you still have a rename left. Meta's rule is per audio: once. Check the audio page in the app before you send a different audio_name, and keep a record of which sounds you have already named.

For a series, plan names as a batch: one agreed pattern, reviewed once, and then applied in every container. That also makes later search and reporting easier, since your own records and the name on Instagram agree.

The container below sets the name at creation, which spends the single rename on purpose rather than by accident.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume