---
title: "Discussion on \"Building an Image-to-Tattoo Workflow Without Turning It Into a Generic Image Filter\" | Hashnode"
description: "Discussion on \"Building an Image-to-Tattoo Workflow Without Turning It Into a Generic Image Filter\". What I learned about multipart uploads, quota checks, job locks, OAuth state, and privacy while adding Image to Tattoo to an existing AI product."
url: "https://hashnode.com/posts/building-an-image-to-tattoo-workflow-without-turning-it-into-a-generic-image-filter/6a6abbce79ac0e070dd471b3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building an Image-to-Tattoo Workflow Without Turning It Into a Generic Image Filter](https://wslabs.hashnode.dev/building-an-image-to-tattoo-workflow-without-turning-it-into-a-generic-image-filter?utm_source=hashnode&utm_medium=feed)

What I learned about multipart uploads, quota checks, job locks, OAuth state, and privacy while adding Image to Tattoo to an existing AI product.

Jul 30 · 11 min read · wslabs.hashnode.dev  
Read the article

## Written by

[Shi Warren](https://hashnode.com/@wslabs)

@wslabs · San Francisco, CA

  
[View profile](https://hashnode.com/@wslabs)

Building browser-side workflow & privacy tools

Building browser-side workflow, privacy, and metadata utilities. Interested in AI workflows, semantic SEO, and lightweight developer tools.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
