A: Hi nl8 🙌

1. Magic Links and CDN Usage:

You’re right to consider how Magic Links could impact your credit usage, especially with dynamic content like OG image creation. To clarify, behind the Magic URL, we perform the same operations as you would with our API. The process is identical: we generate the image or PDF based on your template and parameters. Once the file is generated using the Magic URL, it is cached via our CDN. This means that subsequent requests to the same URL will serve the cached version without consuming additional credits. However, even a single character change in the URL will invalidate the cache, as it will be treated as a new conversion. Our main goal with Magic URL is to provide a simple and efficient way to generate images or PDFs from a template. So yes, Magic URL will consume credits just as if you were doing the same thing through our API. You can also see the API activity on your dashboard when you generate an image or PDF via Magic URL by visiting this link: https://markupgo.com/dashboard/activity

2. Using toDataURL():

No, we do not use toDataURL() locally. Our image and PDF generation process is handled on our servers, ensuring the best possible performance and compatibility across different platforms.

3. Stability: Browser Cache or Blob Storage?

For stability, we utilize CDN caching rather than relying on browser cache or blob storage. This approach allows us to efficiently manage and serve assets globally, reducing load times and ensuring consistent performance.

4. Base64 Encoding/Decoding:

We only support Base64 as a buffer response; input is not available. You can use the buffer response for saving the file on your server or for post-processing jobs. You just need to add the ‘buffer’ key to your conversion URL. Please check out this page: https://markupgo.com/docs/api/image#getting-buffer-response

We hope this helps. Feel free to ask any questions ❤️