We have partnered with PDF Tools from Switzerland to rework the Compress PDF feature. We are now able to significantly reduce the file size while maintaining target quality. Therefore, we provides various optimization profiles to create PDF documents for specific target needs: web, printing, archiving, scanned documents and a profile for maximal size reduction. You can read more about these profiles here.
For over a year now, we have been actively working on the CloudConvert API v2. Today, we finally release the preview of API v2 for public testing.
Under the hood, v2 is a complete rewrite. We did some architectural changes which allow us to scale more efficient and to be more flexible for future extensions.
API v2 introduces Jobs. Each Job consists of at least one Task. For example: The first task of a job could be importing the file from a S3 bucket. The second task could be converting this file to a different format and the final task of the job could be exporting the file again to a S3 bucket. A single job can process multiple files and it is possible to do multiple operations with the same set of files. This often requested feature will help to increase the flexibility of using our API.
For some tasks, there are multiple engines available. For example, it is possible to convert DOCX files with the Office engine or the LibreOffice engine. The available options differ based on the used engine. Also, you can set an engine version to use. For example, you can set a fixed LibreOffice version to use which makes sure that this version is used, even if we update the default version of LibreOffice. There is an API for each task type available that shows the available engines, versions and their options.
With API v2 you can execute arbitrary FFMPEG, Imagemagick and Graphicsmagick commands. It is now also supported to use commands with multiple input files.
You can now create multiple API keys with different scopes. This allows fine granular access control. We have implemented an OAuth 2.0 server and it is possible to perform requests in behalf of clients, without asking for API keys.
The Sandbox API is a playground for development purposes and integration tests. It allows unlimited requests at no charge but with a fixed set of whitelisted input files only (via MD5 checksum).
There is much more that has changed. Check out the docs of API v2!
The API v2 is now available as "preview". This means the API v2 is not feature complete and there are still bugs. Please do not use v2 in production yet - we might need to temporary take it down or change endpoints without prior notice. However, we encourage you to try out API v2 and we would like to get your feedback! Is there something about API v1 you would like to get changed in v2? Now is the right time to tell us!
In the coming weeks we will update the official SDKs for v2 compatibility. The release of API v2 is planed later this year.
With the release of API v2 we will continue support of API v1 for at least two more years.
The General Data Protection Regulation (GDPR) is the new legal framework of data protection across the EU. Starting 25th May 2018 it will be enforceable. This post clarifies how CloudConvert complies with the GDPR and what our customers can do to be compliant.
In the terms of the GDPR, CloudConvert takes two different roles: CloudConvert is classed as data controller, if it provides services to end customers and directly collects or processes personal data. CloudConvert is classed as processor, if it processes data on behalf of a data controller (typically a customer of CloudConvert).
In short, we do collect:
We do share:
CloudConvert commits to:
If you are an organisation and use CloudConvert to process your customers files, we are typically acting as processor. This is the case if you collect personal data and send them to us for conversion, for example via our API.
As a processor, CloudConvert commits to:
In accordance to Art. 28 GDPR it is possible to sign a data processing agreement with us. This binds us legally to the proper processing of data in accordance to the GDPR. Therefore, contact us.
The CloudConvert website / HTML to PDF, JPG and PNG converter is often used to generate PDF files or thumbnails. Currently, we are using a proven, WebKit-based engine. However, there are use cases that require an even more modern rendering. We are currently experimenting with automating the Chrome browser for this matter.
There is a new option available to enable Chrome for converting HTML files or websites. This option is named "use_chrome" when using our API.
Please note that currently not all of the pre-existing options are available when using Chrome instead of the current engine. The possible options are:
When converting to PDF:
When converting to JPG/PNG:
We are looking forward to get your feedback about this new feature. In particular we are interested if there are any formatting issues or if there are required options missing.
AWS Lambda is an event-driven compute service which runs your code (Lambda functions) in response to events, such as changes to data in an Amazon S3 bucket. The CloudConvert API can be used to automatically convert all files, added to a specific S3 bucket. Typical use cases are converting all office documents to PDF, creating thumbnails or encoding videos.
We have created a GitHub repository with an example Lambda function. To get it running, follow these instructions:
CLUDCONVERT_API_KEYto your personal API key.
AWS_SECRET_ACCESS_KEYfor downloading and uploading from/to your S3 bucket.
outputformataccording to your need. All possible options can be identified using the API Console.
Our Amazon S3 integration is a well used feature. Besides S3 we now have integrated OpenStack Storage (Swift), Microsoft Azure File Storage and Google Cloud Storage. You can use any of these file storage solutions as input and output for CloudConvert conversions. Our API Console has been updated and can be used to live-test the new storage options.