{"id":1129,"date":"2026-07-04T06:03:23","date_gmt":"2026-07-03T23:03:23","guid":{"rendered":"https:\/\/sumberlaba.com\/index.php\/2026\/07\/04\/the-ultimate-guide-to-the-best-tools-for-creating-code-snippets-2024\/"},"modified":"2026-07-04T06:03:23","modified_gmt":"2026-07-03T23:03:23","slug":"the-ultimate-guide-to-the-best-tools-for-creating-code-snippets-2024","status":"publish","type":"post","link":"https:\/\/sumberlaba.com\/index.php\/2026\/07\/04\/the-ultimate-guide-to-the-best-tools-for-creating-code-snippets-2024\/","title":{"rendered":"The Ultimate Guide to the Best Tools for Creating Code Snippets (2024)"},"content":{"rendered":"<h1>The Ultimate Guide to the Best Tools for Creating Code Snippets (2024)<\/h1>\n<p>In the modern development landscape, code snippets are the lifeblood of communication between developers, designers, and technical writers. Whether you&#8217;re documenting an internal API, writing a tutorial on your personal blog, sharing a quick fix on Stack Overflow, or composing a tweet about a clever one-liner, the way you present your code directly affects its readability, impact, and shareability. The days of copying raw text into a message are long gone; today, developers expect syntax-highlighted, visually polished, and easily embeddable code blocks that integrate seamlessly into their workflows. However, with an overwhelming number of tools available\u2014from lightweight screenshot utilities to full-featured cloud IDEs\u2014choosing the right one for your specific needs can be paralyzing. This guide aims to cut through the noise by presenting a comprehensive, step-by-step walkthrough of the best tools for creating code snippets in 2024, accompanied by practical tips, comparative data, and answers to common questions.<\/p>\n<p>Before diving into the tools themselves, it is crucial to understand that the term &#8220;code snippet tool&#8221; is a broad umbrella. Some tools excel at generating beautiful, stylized images of code for social media and presentations (like Carbon and Snappify), while others focus on creating live, interactive embeddable code (like CodePen and CodeSandbox). Still others are dedicated snippet managers that help you store, search, and reuse your own personal collection of code fragments (VS Code Snippets, SnippetsLab, or Dash). The best tool for you depends entirely on what you intend to do with the final snippet: Is it for aesthetic display? For interactive demonstration? For personal reference? Or for collaborative editing? By the end of this tutorial, you&#8217;ll not only know the most popular tools by name but also how to select, configure, and combine them into a powerful snippet pipeline that saves you hours every week. We&#8217;ll cover desktop apps, web services, command-line utilities, and editor extensions, giving you a complete toolkit to handle any coding communication scenario.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/via.placeholder.com\/800x600\/4a90d9\/ffffff?text=best%20tools%20for%20creating%20code%20snippets\" alt=\"Article illustration\" style=\"display:block;margin:20px auto;max-width:100%;height:auto;border-radius:8px;\" \/><\/p>\n<h2>Step-by-Step Guide to Choosing and Using Code Snippet Tools<\/h2>\n<h3>Step 1: Identify Your Primary Use Case and Audience<\/h3>\n<p>The very first step in creating effective code snippets is to ask yourself: who will see this, and in what context? This question is far from trivial; it dictates every subsequent decision you make regarding tooling, formatting, and distribution. For example, if you are preparing slides for a conference presentation, your snippet needs to be large, readable from a distance, and visually striking\u2014tools like Carbon or Snappify that generate high-resolution screenshots with custom themes are your best bet. Conversely, if you are contributing to a technical blog post written in Markdown, you will likely want a text-based snippet with proper syntax highlighting generated by a service like GitHub Gist or a local snippet library that outputs Markdown fenced code blocks with language tags. If you are teaching a live coding session, an interactive environment like CodePen or Replit allows your audience to run the code immediately. And if you are simply building a personal knowledge base, a dedicated snippet manager like SnippetsLab (macOS) or VS Code&#8217;s built-in snippet system will let you quickly store and retrieve code without ever leaving your editor. Take five minutes to write down your typical snippet use cases\u2014documentation, social sharing, collaboration, personal reuse\u2014and rank them by frequency. Your tool selection will be far more focused and productive as a result.<\/p>\n<h3>Step 2: Set Up a Dedicated Snippet Manager for Personal Reuse<\/h3>\n<p>Once you understand your audience, the next logical step is to build a personal repository of reusable code fragments. Relying on your memory or a scattered collection of plain text files is a recipe for inefficiency. A proper snippet manager offers instant search, tagging, syntax highlighting, and even the ability to paste snippets directly into your editor. Among the most powerful options is <strong>VS Code&#8217;s built-in Snippet system<\/strong>, which allows you to define global or language-specific snippets in JSON format. You can type a prefix (e.g., &#8220;clg&#8221;) and have a full console.log statement inserted instantly. For a more visual approach, <strong>SnippetsLab<\/strong> (macOS) provides a beautiful interface where you can organize snippets into folders, add Markdown notes, and sync via iCloud. <strong>Dash<\/strong> (macOS and iOS) doubles as an API documentation browser and snippet manager, while <strong>Lepton<\/strong> is an open-source alternative that supports code snippet sharing via Gist. On Windows, <strong>CodeBox<\/strong> is a popular lightweight manager with a clean UI. Setting up one of these tools is a one-time investment that pays for itself dozens of times over. To start, create a new snippet for a common pattern you use daily\u2014like a boilerplate function, a common loop, or a database connection string\u2014and assign it a memorable prefix. As you work, gradually add more snippets, grouping them by language or project. The goal is to eliminate repetitive typing and reduce the friction of looking up code you&#8217;ve written before.<\/p>\n<table>\n<thead>\n<tr>\n<th>Tool<\/th>\n<th>Platform<\/th>\n<th>Type<\/th>\n<th>Pricing<\/th>\n<th>Key Feature<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>VS Code Snippets<\/td>\n<td>Cross-platform (any editor)<\/td>\n<td>Editor extension<\/td>\n<td>Free<\/td>\n<td>Prefix-based insertion, JSON config<\/td>\n<\/tr>\n<tr>\n<td>SnippetsLab<\/td>\n<td>macOS, iOS<\/td>\n<td>Desktop app<\/td>\n<td>Free (limited) \/ Paid<\/td>\n<td>Folder organization, iCloud sync<\/td>\n<\/tr>\n<tr>\n<td>Dash<\/td>\n<td>macOS, iOS<\/td>\n<td>Doc &#038; snippet manager<\/td>\n<td>Paid (one-time)<\/td>\n<td>Integrates with 200+ API docsets<\/td>\n<\/tr>\n<tr>\n<td>Lepton<\/td>\n<td>Cross-platform (Electron)<\/td>\n<td>Desktop app<\/td>\n<td>Free (open source)<\/td>\n<td>Gist integration, Markdown support<\/td>\n<\/tr>\n<tr>\n<td>CodeBox<\/td>\n<td>Windows, macOS<\/td>\n<td>Desktop app<\/td>\n<td>Free<\/td>\n<td>Lightweight, clean UI<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Step 3: Create Aesthetic Screenshots with Carbon, Snappify, and Polacode<\/h3>\n<p>When your snippet needs to stand out on social media, a presentation, or a portfolio, a plain code block simply won&#8217;t cut it. You need a beautiful, stylized image that draws the eye and conveys professionalism. The undisputed leader in this space is <strong>Carbon<\/strong> (carbon.now.sh), a free web tool that lets you paste code, choose from dozens of syntax themes (e.g., One Dark, Dracula, Nord), adjust the window frame style, and even add shadow effects. Carbon exports as PNG or SVG, and its URL-based parameters make it easy to share a specific snippet configuration. A major update in 2023 added support for animated backgrounds and custom fonts, further increasing its appeal. For those who want even more polish, <strong>Snappify<\/strong> (snappify.com) offers a similar service but with a modern twist: it allows you to export snippets as videos (great for demos), includes a rich text editor for adding annotations, and has a comprehensive template gallery. Snappify&#8217;s free tier is generous, but the paid plan unlocks higher resolution exports and team sharing. If you prefer to stay within your editor, <strong>Polacode<\/strong> (a VS Code extension) lets you take a screenshot of a selected code block directly from your IDE, giving you full control over the background, padding, and theme without leaving your workflow. Polacode is particularly useful when you want to capture code that includes line numbers or specific error highlights. For maximum consistency, consider building a small collection of &#8220;snippet templates&#8221; with your brand colors and preferred font\u2014then you can reuse them across multiple platforms without reconfiguring each time.<\/p>\n<h3>Step 4: Generate Embeddable, Interactive Code with CodePen, CodeSandbox, and JSFiddle<\/h3>\n<p>Not all snippets are meant to be static images. When you want to share a working piece of code that the reader can immediately edit and run, you need an interactive environment. <strong>CodePen<\/strong> is the most popular choice for front-end demos (HTML, CSS, JavaScript) because it provides a clean editor split into HTML, CSS, and JS panels, plus a live preview pane. You can save &#8220;Pens&#8221; that are publicly viewable and embeddable via an iframe, making them perfect for blog posts and documentation. CodePen also supports extensions like the ability to add external libraries (e.g., jQuery, React, D3) with a single click. For more complex projects requiring multiple files, a server-side language, or a full web app environment, <strong>CodeSandbox<\/strong> is a better fit. It is essentially a cloud IDE that supports Node.js, React, Vue, Angular, and many other frameworks, and it can even be synchronized with GitHub repositories. CodeSandbox exports an embeddable URL that gives readers a fully functional IDE within your blog page. On the lighter side, <strong>JSFiddle<\/strong> remains a reliable standby for quick JavaScript or jQuery snippets, especially when you want to test something rapidly without creating a whole Pen. Each of these tools allows you to control the visibility (public\/private), add description and tags, and fork copies of others&#8217; work. For maximum reach, consider cross-posting important snippets to both a static image service (for social previews) and an interactive service (for depth). Remember that interactive embeds can slow down page load times, so use them judiciously\u2014typically one or two per article.<\/p>\n<h3>Step 5: Leverage CLI-Based and Quick Capture Tools (Raycast, Snip, and More)<\/h3>\n<p>Sometimes you need to share a snippet in seconds without opening a browser, an editor, or a web service. This is where command-line and quick capture tools shine. On macOS, <strong>Raycast<\/strong> has become an indispensable productivity tool thanks to its extensive plugin ecosystem. There are multiple snippet-related extensions: you can create a code snippet from clipboard content, format it with syntax highlighting, and upload it directly to Cloudinary or an image host\u2014all without leaving your keyboard. Similarly, <strong>Alfred<\/strong> (with the Powerpack) offers a \u201cClipboard History\u201d feature that can be extended to store snippets as text, but its workflows can also push code to Carbon or GitHub Gist via custom scripts. For Windows users, <strong>Snip<\/strong> (by Microsoft) is a simple but effective screenshot tool that allows you to capture a selected portion of your screen\u2014including a code editor window\u2014and quickly annotate it. However, for code-specific needs, <strong>ShareX<\/strong> (Windows) is far more powerful: it supports custom uploaders (e.g., to Imgur, FTP, or your own server) and can even capture a scrolling screenshot of a long code file. Linux users can rely on <strong>gnome-screenshot<\/strong> combined with command-line image editing via ImageMagick. The key advantage of CLI\/quick capture tools is speed: you can bind a global hotkey to take a snippet screenshot, have it automatically uploaded, and receive a shareable link in less than three seconds. This workflow is ideal for Slack channels or real-time pair programming sessions where you need to show a piece of code instantly. To set this up, choose a tool, define a hotkey (e.g., Cmd+Shift+4 for a region capture), and configure the output destination (local folder or cloud service). Then test it by capturing a random piece of code and sharing the link with a colleague\u2014you&#8217;ll be convinced of its utility immediately.<\/p>\n<h3>Step 6: Automate Snippet Creation with Workflows (Keyboard Maestro, Alfred, and Build Scripts)<\/h3>\n<p>Once you&#8217;ve identified the tools you use most frequently, the next level of efficiency comes from automation. Repetitive tasks\u2014such as copying a code selection, opening Carbon, pasting it, adjusting settings, downloading the image, and then uploading it to your blog\u2014can be reduced to a single key combination using macro tools. <strong>Keyboard Maestro<\/strong> (macOS) is the gold standard for this; you can create a macro that copies the selected text from your editor, opens Carbon&#8217;s URL with that text as a parameter (Carbon supports URL-based content via the `code` query parameter), waits for the page to load, takes a screenshot of the browser viewport, and saves it to a predefined folder\u2014all in the background. There are also ready-made Alfred workflows available (for example, &#8220;Carbon Snippet&#8221; by various developers) that accomplish the same thing with fewer steps. On Windows, <strong>AutoHotkey<\/strong> scripts can be written to simulate the same sequence of actions. Even simpler: if you prefer not to write scripts, you can use a service like <strong>Shottr<\/strong> (macOS) which has a built-in &#8220;Code to image&#8221; feature that automatically applies a dark background and monospace font when you capture a code region. Automation should also extend to organization. Many developers use a build step in their static site generator (like Hugo or Jekyll) that automatically converts code blocks in Markdown into beautiful images using Carbon&#8217;s API\u2014this guarantees consistent styling across all articles. The time you invest in setting up these automations will save you dozens of hours over the course of a year. Start with one simple macro (e.g., copy code \u2192 upload to Gist \u2192 copy URL) and gradually expand to more complex workflows as you identify new repetitive tasks.<\/p>\n<h3>Step 7: Store and Share Your Snippets with Cloud Services (GitHub Gist, Notion, and More)<\/h3>\n<p>Finally, no snippet ecosystem is complete without a robust storage and sharing backend. While desktop managers handle personal organization, cloud-based services allow you to share snippets with the world or with your team. <strong>GitHub Gist<\/strong> is the de facto standard for public code sharing: each gist gets its own URL, can be cloned as a Git repository, and supports embedding via a script tag. Gists also have version history, comments, and the ability to fork\u2014a powerful feature for collaborative debugging. For team environments, <strong>Notion<\/strong> has become a popular wiki-like platform that allows rich code blocks with syntax highlighting, inline comments, and database capabilities. You can create a central snippet database with tags, dates, and project associations. <strong>GitLab Snippets<\/strong> (for GitLab users) offer similar functionality. For quick, disposable sharing\u2014like pasting a block of code for code review\u2014services like <strong>pastebin.com<\/strong> or <strong>dpaste.org<\/strong> work well but lack syntax highlighting and versioning. More advanced users may set up a self-hosted solution like <strong>Mist.io<\/strong> or <strong>Hastebin<\/strong> using Docker. The choice between these services depends on your need for privacy (public vs. private), editing history, and team access. A practical strategy is to use GitHub Gist for public-facing snippets (e.g., for your blog) and Notion for internal team snippets. Make sure to maintain a consistent naming convention and tag system across all platforms to keep your snippets searchable. Additionally, many of the tools mentioned in previous steps (CodePen, SnippetsLab, etc.) directly integrate with Gist, so you can push snippets from your editor straight to the cloud with a single hotkey.<\/p>\n<h2>Tips and Best Practices for Creating Code Snippets<\/h2>\n<h3>Tip 1: Show Only the Essential Code \u2014 Trim Everything Else<\/h3>\n<p>The cardinal rule of a good snippet is that it should communicate the idea in the smallest possible surface area. Novice snippet creators often paste entire files\u2014including import statements, boilerplate, and comments that are irrelevant to the point. Instead, isolate the core logic, remove extraneous whitespace, and use comments sparingly but meaningfully. If a reader needs to understand context, add a brief explanatory sentence above the snippet (in natural language) rather than inside the code block. For languages that require dependencies, consider using a tool like CodeSandbox that can bundle the entire project while still focusing the viewer&#8217;s attention on the key function. You should also consistently adhere to a maximum line length (e.g., 80 characters) to avoid horizontal scrolling in embedded environments. When sharing on Twitter or Instagram, keep snippets to around 10\u201315 lines so they remain readable on mobile screens. Finally, use line highlighting (supported by Carbon, CodePen, and VS Code) to direct the viewer&#8217;s eye to the critical lines\u2014highlighting three lines of a 30-line snippet is far more effective than highlighting nothing.<\/p>\n<h3>Tip 2: Maintain a Consistent Visual Style Across All Snippets<\/h3>\n<p>If you publish code snippets regularly\u2014whether on a blog, social media, or documentation\u2014you should establish a visual &#8220;brand&#8221; for your snippets. This means picking a fixed font (e.g., Fira Code, JetBrains Mono, or the classic Source Code Pro), a consistent theme (like Nord, Dracula, or a custom dark theme), and a standard background color (usually dark gray or a soft black). For image-based snippets, also decide on a uniform window frame style (macOS window buttons vs. a simple flat card) and a standard shadow or glow effect. Tools like Carbon let you save your configuration via URL parameters, so you can bookmark a base URL and tweak only the code. For text-based snippets (like in Markdown), choose one syntax highlighter (e.g., Prism.js vs. highlight.js) and stick to it across your site. Consistency not only makes your content look professional but also builds recognition\u2014teams and audiences will instantly associate your visual style with quality code sharing.<\/p>\n<h3>Tip 3: Use Version Control and Metadata for Complex Snippets<\/h3>\n<p>When you create a snippet that is part of a larger project or an evolving codebase, treat it as a mini-software artifact. Add a header comment that includes the date, the purpose, and any relevant links (e.g., to the full source file or documentation). If you use a cloud service like GitHub Gist, always write a meaningful description and use the filename extension to trigger proper syntax highlighting. For snippets in a team environment, consider using a semantic versioning pattern or at least a changelog inside the document. This becomes especially important when snippets are used in multiple places (documentation, slide decks, internal wikis) and updates need to be tracked. Some advanced editors and snippet managers allow you to link a snippet to a specific commit or issue in your project management tool. Even a simple text file containing a version number can save hours of confusion when someone later wonders why a snippet they copied last week no longer works.<\/p>\n<h2>Frequently Asked Questions (FAQ)<\/h2>\n<h3>Q1: What is the best free tool for creating beautiful code screenshots?<\/h3>\n<p><strong>A:<\/strong> For purely free and high-quality image generation, <strong>Carbon<\/strong> (carbon.now.sh) remains the top recommendation. It requires no account, supports multiple themes and export formats (PNG, SVG), and is continuously updated. Snappify offers a free tier but limits resolution and some features. Polacode is also free if you use VS Code. Carbon&#8217;s URL-based API also allows you to pass code programmatically, making it easy to automate. However, note that Carbon does not provide a direct embed feature for clickable code\u2014it only outputs images. If you need an interactive embed, CodePen&#8217;s free tier is excellent but yields HTML\/iframes instead of images.<\/p>\n<h3>Q2: How can I share a code snippet securely without exposing sensitive data?<\/h3>\n<p><strong>A:<\/strong> Security is a critical concern, especially when sharing snippets that contain API keys, passwords, or internal logic. The safest approach is to use a service like <strong>GitHub Gist<\/strong> with a \u201cSecret\u201d gist (not private, but not indexed by search engines) and share the link only with trusted parties. Even better, use a pastebin service that supports expiration and password protection (e.g., <strong>PrivateBin<\/strong> or <strong>OneTimeSecret<\/strong>). Before sharing, always replace or remove sensitive values with placeholders like `<YOUR_API_KEY>` or `SECRET`. Additionally, run a quick grep for common patterns (e.g., \u201cpassword\u201d, \u201csecret\u201d, \u201ckey\u201d) before pasting. For internal teams, a self-hosted snippet manager (like SnippetsLab with cloud sync disabled) offers the highest security.<\/p>\n<h3>Q3: Can I embed a code snippet into a WordPress blog post without a plugin?<\/h3>\n<p><strong>A:<\/strong> Yes. WordPress&#8217;s block editor (Gutenberg) now includes a native \u201cCode\u201d block that applies simple monospace formatting, but it lacks syntax highlighting. For better looks, you can use services like <strong>GitHub Gist<\/strong> (paste the embed script into a Custom HTML block) or <strong>Carbon<\/strong> (download an image and insert it like a regular image). Alternatively, you can install a free plugin like \u201cSyntaxHighlighter Evolved\u201d or \u201cCrayon Syntax Highlighter\u201d to render code with full highlighting. If you prefer to avoid plugins, copy your code into an online tool like <strong>Prism.js<\/strong> and use the generated HTML. Always test the mobile responsiveness of your embedded snippet.<\/p>\n<h3>Q4: What is the best way to organize thousands of personal code snippets?<\/h3>\n<p><strong>A:<\/strong> For large collections, a dedicated snippet manager is essential. <strong>SnippetsLab<\/strong> (macOS) allows you to create nested folders, apply tags, and use smart groups based on language or category. You can also sync with iCloud to access snippets on multiple devices. Another powerful approach is to store all snippets as individual files in a dedicated GitHub repository, then use the GitHub REST API to search and retrieve them. A third option is to use <strong>Notion<\/strong> as a database with properties for language, tags, date created, and project association. Notion&#8217;s search is robust, and you can embed the snippets in other pages. Regardless of the tool, use a consistent naming convention\u2014e.g., `javascript\/array-filter.md`\u2014and create a separate folder for each language or framework.<\/p>\n<h3>Q5: Which tool allows me to include the result of the code (e.g., output or logs) next to the snippet?<\/h3>\n<p><strong>A:<\/strong> Interactive environments like <strong>CodePen<\/strong>, <strong>JSFiddle<\/strong>, and <strong>Replit<\/strong> naturally show the output of your code side-by-side or below the code editor. For static images, you can manually combine a screenshot of the code with a screenshot of the output (e.g., from your terminal or browser) using an image editor like Figma or Snagit. There is also a specialized tool called <strong>Instants<\/strong> (instants.dev) that generates beautiful screenshots of code with its console output, but it is more experimental. For documentation purposes, you can use <strong>Markdown<\/strong> with code blocks and then manually add the expected output as a separate code block (e.g., with a \u201cshell\u201d or \u201coutput\u201d language tag).<\/p>\n<h2>Conclusion<\/h2>\n<p>Creating effective code snippets is an art that blends technical precision with visual communication. As we have seen, the ecosystem of tools is rich and varied\u2014from the blazing-fast clipboard utilities like Raycast to the gorgeous, shareable images from Carbon and Snappify, from the versatile snippet managers that keep your personal library organized to the interactive sandbox environments like CodePen that let your code come alive. The key takeaway is to stop relying on ad-hoc methods (screenshots of your text editor, plain text pastes, or generic image editors) and instead build a purposeful toolkit that matches each of your use cases. Start by setting up one personal snippet manager and one image generator, then gradually integrate an interactive tool and a cloud storage service. Automate repetitive steps using macros or command-line scripts. By following the step-by-step process outlined in this guide, you will not only save countless hours but also elevate the professionalism of your code sharing. Remember that the goal is not just to show code, but to make it understandable, attractive, and reusable for your audience. Now open your editor, select that clever function you wrote yesterday, and give it the presentation it deserves.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Ultimate Guide to the Best Tools for Creating Code Snippets (2024) In the modern development landscape, code snippets are the lifeblood of communication between developers, designers, and technical writers. Whether you&#8217;re documenting an internal API, writing a tutorial on your personal blog, sharing a quick fix on Stack Overflow, or composing a tweet about &hellip; <\/p>\n","protected":false},"author":2716,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[],"tags":[],"class_list":["post-1129","post","type-post","status-publish","format-standard","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/posts\/1129","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/users\/2716"}],"replies":[{"embeddable":true,"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/comments?post=1129"}],"version-history":[{"count":0,"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/posts\/1129\/revisions"}],"wp:attachment":[{"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/media?parent=1129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/categories?post=1129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sumberlaba.com\/index.php\/wp-json\/wp\/v2\/tags?post=1129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}