loader.to Button API migration

Migrate a loader.to Button API endpoint to Video Download API

Searching for https://loader.to/api/button/?url=? Use this guide to map that embed intent to the current Button API reference, pricing, docs, signup, and support paths.

Open Button API Create API key Open API docs

Endpoint mapping

Replace the host, then validate parameters

Old search pattern

https://loader.to/api/button/?url=VIDEO_URL&f=FORMAT

Button API pattern

https://p.savenow.to/api/button/?url=VIDEO_URL&f=FORMAT

p.savenow.to is the default shared API host used in public examples. If your dashboard shows a custom API hostname, use that account-specific host instead.

Migration map

Map loader.to Button API parameters to the current embed path

This page avoids assumptions about an existing integration. Start by preserving the request shape, then confirm whether a hosted button or a REST API migration gives your product enough control.

loader.to Button API query

Video Download API path

Migration note

https://loader.to/api/button/?url=VIDEO_URL

https://p.savenow.to/api/button/?url=VIDEO_URL

Keep the same required video URL concept and update the host to the configured Button API host.

f=mp3 or a video quality

f=mp3, f=mp4, f=720, or another supported output value

Validate each format against the source videos your product accepts before switching production embeds.

color, linkUrl, css

Preserve styling and redirect parameters when they are part of the hosted button experience.

Hosted button iframe

Hosted Button API iframe or REST API flow

Use REST API instead when you need API keys, progress polling, and custom application states.

Implementation

Move from endpoint lookup to a tested migration

Keep the first pass small: one current embed, one Video Download API Button API equivalent, one pricing estimate, and one REST API check if you need authenticated server-side control.

Read API docs Get migration help

Step 1
Copy the current loader.to Button API URL shape and list every parameter your pages send.
Step 2
Replace the endpoint host with the Video Download API host and keep url as the required source-video parameter.
Step 3
Open the Button API reference to confirm optional format, color, linkUrl, and css behavior.
Step 4
Use pricing and docs to decide whether the embed is enough or whether REST API control is a better production fit.
Step 5
Create an API key before testing any REST migration path that needs authenticated download jobs or progress polling.

Decision path

Choose the Button API embed or the REST API workflow

Use Button API

Choose this path for a compact hosted downloader button inside an existing page, result list, or template.

Open Button API

Use REST API

Choose this path when your product needs authenticated jobs, progress polling, response handling, or custom UX.

Compare REST API

Estimate pricing

Model audio, MP4, subtitle, transcript, and duration costs before moving production traffic.

View pricing

FAQ

loader.to Button API migration questions

What replaces https://loader.to/api/button/?url=?

Use the Video Download API Button API URL pattern on the configured API host: /api/button/?url=VIDEO_URL with optional format, color, link URL, and CSS parameters.

Should I migrate to Button API or REST API?

Use Button API when you need a compact hosted embed. Use the REST API when your application needs API-key authenticated jobs, progress polling, custom response handling, subtitles, transcripts, thumbnails, or metadata workflows.

Where do I check pricing before switching traffic?

Open the pricing calculator to estimate pay-as-you-go costs by output type, volume, and duration before moving production embeds or REST requests.

Can I get help mapping an existing loader.to Button API integration?

Yes. Share the current embed URL shape, expected formats, traffic volume, and migration goal through the contact page so support can point you to the right Button API or REST API path.