Shorts 2026 changes: heart, no dislike, Save, and your export file
Which of the YouTube Shorts changes from June and July 2026 affect the file you export, and which only change the on-screen ask. Sources and dates included.

None of the 2026 button changes alter the file you export. Per Wikipedia's page on YouTube Shorts (third-party, read 2026-10-05), Shorts replaced the like button with a heart and dropped the dislike button in June 2026, then added a Save button in July 2026. These are interface changes. The file limits come from YouTube Help, which says a Short can be up to 3 minutes long and uploaded at a maximum of 1080p (read 2026-10-05). So your 9:16, 1080x1920 file stays the same; what you may change is the line of text you burn in.
Change by change
The table separates what the sources say from what it means for production.
| Item | Source | Export impact |
|---|---|---|
| Heart replaces like (June 2026) | Wikipedia, third-party | None to the file; reword any 'like' ask |
| Dislike button dropped (June 2026) | Wikipedia, third-party | None to the file |
| Save button added (July 2026) | Wikipedia, third-party | None to the file; optional end-card ask |
| Length up to 3 minutes | YouTube Help | Cut to 180 seconds or less |
| Maximum 1080p | YouTube Help | Do not render above 1080x1920 |
What you can do with Sume
Reword a spoken or burned-in 'smash the like button' with new caption cues; see video captions. Cut a longer video to 180 seconds with video trim, whose duration accepts 0.2 to 900 seconds, so a 180 second cut is one job at $0.02. Render a new sequence at the Timeline 1.0 default of 1080x1920, which matches the YouTube ceiling.
- A spoken 'like' ask cannot be edited out of the audio with these tools; re-record the line or cover it with a new bed.
- Burned-in text can only be replaced by re-cutting from the clean source, not by painting over it.
- Check the dates against YouTube's own announcements: the 2026 button changes are cited here from a third-party page.
Why this is a separate question from file specs
Readers searching for the heart or Save change are usually asking whether the Short needs re-exporting. It does not. Re-export only for a reason in the table's last two rows.
What I could not verify
I could not retrieve a YouTube Help page that describes the heart or Save changes, so those two items rest on Wikipedia alone. Wikipedia is a third-party summary and can be edited, so check the date and wording in YouTube's own announcements before you quote them. The length and resolution facts are from YouTube Help, read on 2026-10-05.
If you publish a Short that asks viewers to like, heart or save, write the ask in plain words and test it on a still. An ask that depends on a button the viewer cannot find costs attention for nothing.
Re-exporting only when needed
A common mistake after an interface change is to re-render a whole back catalog. Do not. The only files worth touching are those that say, in audio or on screen, something the new buttons make wrong, for example a burned-in line telling viewers to hit a button that no longer exists. For those, go back to the clean source, change the caption cues, and burn again; the cost is one caption job per clip.
To sum up: the button changes are interface changes, the 3 minute and 1080p limits are file limits, and only the second group decides how you export. Keep 1080x1920, stay at or under 180 seconds, and treat any burned-in call to action as editable text that you can re-burn from a clean source.
Sources
Related posts
More in Media tools
- YouTube Shorts custom thumbnail: Studio on a computer, 9:16 still
A custom Shorts thumbnail is 9:16, minimum 640 px on the short side, and can only be added in YouTube Studio on a computer. Export one still with Sume.
- YouTube thumbnail 2 MB on mobile vs 50 MB on desktop: video still
YouTube custom thumbnails are limited to 2 MB on mobile and 50 MB on desktop, JPG or PNG. Cut a still from a Sume clip and choose JPEG to stay under 2 MB.
- How to assemble a long-form video with the Timeline 1.0 API
Timeline 1.0 renders one audio spine plus 1 to 200 ordered video slots into one MP4. Every URL must be Sume-hosted; the plan preflight is unbilled.
- How to burn captions onto a video with the Sume API
Send a public HTTPS video URL to POST /v1/video-captions and get a job-backed captioned video, timed by speech-to-text or by text you supply.
Written by Sume