DIVIDE UNA IMAGEN ALTA EN UNA PUBLICACIÓN QUE SE REVELA
The tap the post trend is the simplest engagement trick on X, and it works because of how the platform previews a multi-image post. Attach several images and X does not show them at full size — it lays them out in a small cropped grid. Each piece is squeezed into a tile and trimmed to fit, so a tall image sliced into pieces looks fragmentary and strange while someone is scrolling. That incompleteness is the hook. To see what it actually is, they have to tap the post.
This tool does the slicing. Drop in a tall image, choose how many pieces you want, and it cuts them top to bottom, numbers them in upload order, shows you a simulation of how the X timeline will crop the result, and hands you everything as a single ZIP. Nothing is uploaded — the cutting happens in your browser with the Canvas API.
The tap the post trend is constantly confused with the tap and hold trend, and it is worth being precise about the difference because it decides which tool you need. Tap and hold hides a second picture inside a single transparent PNG, using the alpha channel to show one image against the timeline's white background and another against the viewer's dark interface. It is a beautiful trick and a fragile one: post it from the X mobile app and the file is re-encoded to JPEG, the alpha channel vanishes, and the hidden image is gone.
Tap the post has none of that fragility. There is no transparency to lose, so nothing about re-encoding, file format, or upload route can break it. It looks the same to a viewer in light mode as in dark mode. It works from the mobile app. The only thing you can get wrong is the order of the pieces, and the numbered filenames exist to stop that happening. If you have fought with a tap and hold image that refuses to cooperate, this is the technique that just works.
The reveal has to be worth the tap. Full-body portraits work because the grid crops the subject in half. Vertical landscapes work because the timeline shows a slice of sky that means nothing on its own. Tall illustrations, long jokes with the punchline at the bottom, before-and-after comparisons stacked vertically, and text posts whose ending is hidden in the last piece all work for the same reason: the preview raises a question that only opening the post can answer.
Wide and square images are the common mistake. If the grid preview already shows the whole picture, there is nothing to reveal and no reason to tap. If your image is wide, switch the cut direction to vertical strips — the tool does this automatically when it detects a landscape source — though a tall source remains the stronger choice.
X is the platform this is designed for, because the cropped grid preview and the full-size gallery on tap are exactly the two states the trick needs. Instagram carousels behave differently, showing one image at a time rather than a cropped grid, so the timeline confusion never happens — though a sliced sequence can still work as a swipe-through reveal. Because nothing here depends on transparency, no platform can silently destroy the effect the way they destroy tap and hold images; the worst that happens is the preview layout differs.
It is a curiosity format. You slice one tall image into several pieces and upload them as a single X post, which X then displays as a cropped grid of small tiles. The timeline preview looks incomplete or confusing, so people tap the post to open the gallery, where the pieces read in order and the full picture resolves. Unlike the tap and hold trend it uses no transparency at all, so nothing can strip the effect.
They are two separate techniques that trend together and are constantly confused. Tap and hold hides a second image inside one transparent PNG using the alpha channel, and it breaks if that alpha channel is ever discarded. Tap the post slices one image into several ordinary images and relies purely on upload order and how X crops multi-image previews. Tap the post is far more robust: it survives the mobile app, survives re-encoding, and looks the same in light and dark mode.
It is the entire trick. X arranges a four-image post in a fixed grid, so if the pieces go up in the wrong sequence the picture is scrambled and the reveal fails. The exported files are numbered 1 to 4 for exactly this reason — upload them in numerical order and the geometry takes care of itself. If your posting client lets you drag to reorder after attaching, check the numbers before you post.
Tall ones. The taller and narrower the source, the more dramatic the payoff, because the timeline grid can only show a small cropped fragment of each piece. Full-body portraits, vertical landscapes, tall illustrations, and long text jokes all work well. A wide or square image gives the game away in the preview and produces a weak reveal.
No. The slicing happens entirely in your browser using the Canvas API, and the ZIP is assembled in memory on your own device. Nothing is transmitted, nothing is stored, and there is no account to create.
Partly. The technique needs a platform that crops a multi-image post into a grid preview and then shows the individual images in full when opened. X is the case it is designed around. Instagram carousels show one image at a time rather than a cropped grid, so the timeline confusion that drives the tap never happens, though a sliced sequence can still work as a swipe reveal. Unlike the tap and hold trick, nothing here depends on transparency, so no platform can silently destroy it.
No watermark, no limit, no signup, and no cost. The tool runs in your browser, so there is no server capacity to meter.