<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">Big Chungus</span> belongs as a tag, and if it's a <span class="tag">Meta Easter egg</span>, that's a tag, too. Fully describing an image like <code>Big Chungus standing at the top of a stair case mocking Elmer Fudd, like a true Reddit gamer moment</code> should be done in the description.</p>
<p>We also have some "meta" tags — <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. In some rare cases, uploads may become broken, if this is the case, doing a local optimization on your comptuer and then reuploading would solve this issue.</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>
<h4>MP4/WEBM</h4>
<p> Thats right! We support MP4 and WEBM, have fun.
<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>
<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">Big Chungus</span> belongs as a tag, and if it's the <span class="tag">PS4 Game by Hello Games</span>, that's a tag, too. Fully describing an image like <code>Big Chungus, standing, mocking, Elmer Fudd, Meta Easter Egg, Reddit moment</code> should be done in the description.</p>
<p>For instance, the fact that an image contains <span class="tag" data-tag-category="character">Big Chungus</span> belongs as a tag, and if it's a <span class="tag">Meta Easter egg</span>, that's a tag, too. Fully describing an image like <code>Big Chungus standing at the top of a stair case mocking Elmer Fudd, like a true Reddit gamer moment</code> should be done in the description.</p>
<p>We also have some "meta" tags — <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. In some rare cases, uploads may become broken, if this is the case, doing a local optimization on your comptuer and then reuploading would solve this issue.</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>
<h4>MP4/WEBM</h4>
<p> Thats right! We support MP4 and WEBM, have fun.
<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>
<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>For instance, the fact that an image contains <span class="tag" data-tag-category="character">Big Chungus</span> belongs as a tag, and if it's the <span class="tag">PS4 Game by Hello Games</span>, that's a tag, too. Fully describing an image like <code>Big Chungus, standing, mocking, Elmer Fudd, Meta Easter Egg, Reddit moment</code> should be done in the description.</p>
<p>We also have some "meta" tags — <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. In some rare cases, uploads may become broken, if this is the case, doing a local optimization on your comptuer and then reuploading would solve this issue.</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>
<h4>MP4/WEBM</h4>
<p> Thats right! We support MP4 and WEBM, have fun.
<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>