Revision history for Uploading to Derpibooru

UserDateBody
byte[]<div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the site, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains <span class="tag" data-tag-category="character">twilight sparkle</span> belongs as a tag, and if it's the <span class="tag">summer sun celebration</span>, that's a tag, too. Fully describing an image like <code>Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe</code> should be done in the description.</p> <p>We also have some "meta" tags &mdash; <span class="tag" data-tag-category="origin">artist:artist name</span> tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted. These should be used where appropriate.</p> <p>Finally, there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try to find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p>We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. <code>librsvg</code> is used to render the images.</p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p>We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way.</p> <h4>JPEG</h4> <p>We use <code>jpegtran</code> to sort out JPEGs, which supports lossless optimization of the entropy encoding scheme used in JPEG compression.</p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing. We use <code>gifsicle</code> and <code>ffmpeg</code> to process GIFs.</p> <h4>SVG</h4> <p>SVG images are left unchanged by uploads.</p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>
byte[]<div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some meta tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the site, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains <span class="tag" data-tag-category="character">twilight sparkle</span> belongs as a tag, and if it's the <span class="tag">summer sun celebration</span>, that's a tag, too. Fully describing an image like <code>Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe</code> should be done in the description.</p> <p>We also have some "meta" tags &mdash; <span class="tag" data-tag-category="origin">artist:artist name</span> tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted. These should be used where appropriate.</p> <p>Finally, there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try to find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. <code>librsvg</code> is used to render the images.</p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <p>We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way.</p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <p>We use <code>jpegtran</code> to sort out JPEGs, which supports lossless optimization of the entropy encoding scheme used in JPEG compression.</p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing. We use <code>gifsicle</code> and <code>ffmpeg</code> to process GIFs.</p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <p>SVG images are left unchanged by uploads.</p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>
Arcaire<% content_for(:robots, true) %><h1>Uploading to Derpibooru</h1> <div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some 'meta' tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> <div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some meta tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>
DragonMaus<h1>Uploading to Derpibooru</h1> <% content_for(:robots, true) %><h1>Uploading to Derpibooru</h1> <div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some 'meta' tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>
byte[]<h1>Uploading to Derpibooru</h1> <div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some 'meta' tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>
liamwhite1<h1>Uploading to Derpibooru</h1> <div class="walloftext"> <p>Uploading content is a piece of cake. You just hit the 'Upload' button and fill in the form. However, there's a few little details we'd like to explain better to you if you're interested.</p> <h2>Metadata</h2> <p>We provide a few fields for metadata - tags are designed to let you group images together, and describe things in terms of their content. We also have a description field, which is intended mostly for people uploading original content to the Booru, or for more detailed description of images or context around the image. It can also be used for audio description of images for people with screenreaders.</p> <p>For instance, the fact that an image contains Twilight Sparkle belongs as a tag, and if it's the Summer Sun Celebration, that's a tag, too. Fully describing an image like "Twilight sparkle standing on the steps in awe at Celestia at the Summer Sun Celebration, wide-eyed in awe" should be done in the description.</p> <p>We also have some 'meta' tags - artist:artistname tags should be used to link an artist name to an image. There are also spoilered or hidden by default tags, which stop NSFW things from popping up when not wanted - these should be used where appropriate.</p> <p>Finally there is the source URL field. This should link to the page on which the image was originally found. If you don't know, leave it blank, but try and find it first.</p> <h2>Scalable Vector Graphic uploads</h2> <p> We support SVG uploads - once we get them on the server we make PNG images out of them, but people can still download and view the SVG version on the links on the image. A <a href="//inkscape.org/en/gallery/item/6206/">customized version of Inkscape</a> is used to render images. </p> <p>We recommend you provide a sensible default resolution with your document - a couple of thousand pixels is plenty!</p> <h2>Optimization</h2> <p>When you upload a GIF, JPEG or PNG, we do some checks on the image once it's been uploaded. Most images have un-needed data in them, which can be safely removed without affecting quality. We use a few tools to do this on your uploads, resulting in smaller file sizes for us to store, and faster page loads for everybody.</p> <h4>PNG</h4> <p> We use <code>optipng</code> to deinterlace and compress PNG images, fixing any encoding issues on the way. </p> <h4>JPEG</h4> <p> We now use <code>jpegtran</code> to sort out JPEGs, which supports <strong>lossless</strong> optimization of the entropy encoding scheme used in JPEG compression. </p> <h4>GIF</h4> <p> GIFs are a bit more complex, as we treat all GIFs as probably animated, and so have to deal with all the frame processing (unlike some tools which just make a thumbnail from the first frame, which we think is a bit cheeky). We use <code>gifsicle</code> to process GIFs. </p> <h4>SVG</h4> <p> SVG images are scrubbed to remove JavaScript tags. We use a custom version of <code>scour.py</code> for this task. We leave editor data alone, so your image should be as editable as it was when you uploaded it. SVG images are scrubbed to remove JavaScript tags. We leave editor data alone, so your image should be as editable as it was when you uploaded it. </p> <h2>Deduplication</h2> <p>We perform perceptual image deduplication using a simple image intensity based mechanism which has proven to be scalable and reasonably reliable over the years. We also provide SHA512 hashes of images in the site, though these are no longer used internally for deduplication.</p> <h2>Workflow</h2> <p>We do all the processing in the background, and while we're doing it, we continue to serve the unoptimized file, so there's no noticeable difference for anyone. It is, however, noteworthy if you intend to download a file, you may wish to wait for the fully processed image to be available. Depending on the file type and file in question, it can take a while to process images - up to 5-6 minutes in some cases - and since we only have limited resources, if there's a queue, this could be a longer wait.</p> <p>Basically, upload, and don't worry about it! We'll handle all the heavy lifting on our end, and once we finish processing the image, it'll be served instead of the old unoptimized one immediately.</p> </div>